Perhaps an option could be added to directly utilize the c function and type functionality

[Angluca]

Maybe can add @ or $ orC.directly use the c function and type,
Perhaps the key to achieving this lies in not checking the types and function names that contain the "@" symbol , All of these are for the C compiler to compile.

u32 screen_width = 200;
u32 screen_height = 200;

//auto gray = @Color { r: 130, g: 130, b: 130, a: 255 };
auto bg_color = @Color { 76, 63, 47, 255 };
@InitWindow(screen_width, screen_height, "quark raylib".data());
@SetTargetFPS(60);
bool is_close = false;

while(is_close != true) {
    @ClearBackground(bg_color);
    @BeginDrawing();
        @DrawText("hello quark".data(), 10, 80, 20, @GRAY);
    @EndDrawing();
    is_close = @WindowShouldClose();
}

and rename 😄

type init_window = @InitWindow

It looks very concise.

[ephf]

I was actually thinking of adding a c header parser, something like

import raylib.h; // <- the '.h' signifies its a c header file

InitWindow(/* ... */); // <- this would be valid

I do also think inline C would be good to implement though, but I think it would be more similar to the asm keyword, I'll see what works best.

[Angluca]

It would be even better if we could directly use the functions and types from the C library. 😄

[ephf]

Added support for extern blocks using curly braces in the latest push in feature/extern-blocks, your example would look something like this

u32 screen_width = 200;
u32 screen_height = 200;

extern {
InitWindow(screen_width, screen_height, "quark raylib");
SetTargetFPS(60);
};

I'll see about adding templating for compiled variable/function names, but for now variable names shouldn't be changed from their quark counterparts so defining them outside should not be an issue.

Also note that the extern block is an expression so it can be used inline as well:

u8* buffer = extern<u8*> { malloc(32) };