Zac Nowicki

Your call. Workarounds exist using `float[]` if you don't need the arbitrary precision or you can also use `jsonb` column (`[1, 2.3, 4]`). `float[]` works for my use case.

At the least, the issue is here and on the driver in case anyone runs into the same problem :sweat_smile:

I'm sorry if this is too critical, but I don't think this frontend is ready yet for documenting general code. Overall presentation The overall presentation feels like a step backwards...

Tangentially, it would be great to have references to Crystal's memory model - even if yellow-taped as unstable - for those of us writing memory-sensitive applications today. `crystal tool hierarchy`...

Yeah I meant to bind `rescue ex : Error` haha. I just ran into this because I typo'd while prototyping, and saw my terminal that runs specs when my files...

@thomasnal I think you misunderstand the direction of the issue. The proposal is to have Jennifer analyze the database itself and build the mapping for you, such that you don't...

I'm not sure when it happened, but it would seem that this is indeed fixed now. :tada: ``` package main; T :: struct($U: int) {} @(require_results) foo :: proc(t: T($U))...

This issue appears to be still reproducible on the latest Odin compiler, and the "workaround" of `m: $T/map[$K]int` still applies.

This appears to still be an issue, per @Kelimion's example above - still segfaults on my machine with latest odin.

@munirehmad Please do not post your token anywhere publicly! It allows anyone access to your bot. I have removed it from your comment, but please reset your token in the...