Recep Aslantas

Hi @v1993, You are right, struct api could return a type but I'm not sure for bringing new type since engines may have an AABB type internally, introducing a new...

Hi @duarm, Sorry for the late response, We can have float int vector conversion as you proposed. I think we can continue with functions for now. FWIW, in the future...

Hi, @offthebus, @Jesse2431 `#define _CRT_SECURE_NO_WARNINGS` should suppress those warnings. It is defined in `cglm/common.h`: https://github.com/recp/cglm/blob/master/include/cglm/common.h#L15-L17 Do you use latest version of **cglm** ?

**cglm** has Swift Package :) Also in the future, **cglm** may add basic C++ operations like operator overloading ( `+=`, `*=`, `-= ) and some other helpers to struct types...

Hi @CaspianA1, This is discussed somehow earlier at: https://github.com/recp/cglm/issues/83 also see https://github.com/recp/cglm/pull/86. If there is a good way to do this we can approach to. Any feedbacks discussions are welcome

@Kharzette thanks, There are some issues discussed at: https://github.com/recp/cglm/issues/83 like: ``` warning: pointers to arrays with different qualifiers are incompatible in ISO C [-Wpedantic] ``` Let's merge this issue with...

Hi @EasyIP2023, I like the proposal but let wait a little bit to get more feedbacks, Currently `glm_vec3()` creates **vec3** from **vec4** or pointer, `glm_vec2()` creates **vec2** from pointer. `glm_vec4(vec3,...

Hi @duarm, Sorry for the delay, I was saw the issue but couldnt reply, > Let's say we have a _circle_vs_aabb2d, should this function live inside aabb2d.h or circle.h? should...

> I think alphabetical is best, and we can always add a macro later. Seems ok to me but for instance `circle_v_aabb` and `aabb_v_circle` can coexist with macro :S using...

> if the api surface is not a problem. No prob :) > I agree, another library which depends on cglm. Nice 👍