goose++ comments

Results 9 comments of


                                            goose++

highly nested comptimes lead to stackoverflow in type infference

This is more of an issue on deeply nested things in general. As long as the codebase is structured in a recursive way, this will be an problem. This input...

highly nested comptimes lead to stackoverflow in type infference

I just pushed a large change to `hir_ty` which removed much of the recursion but the input still crashes for some reason. I must have missed something or misdone something....

Cranelift: JIT assertion failure when using `ArgumentPurpose::StructArgument` on macOS (A64)

Thank you! This is very helpful! In any case, if `StructArgument` isn't meant to be used on a64 then there should probably be a better error message than an assertion...

maybe add functions for directly working with function or struct types

Yes, this would be useful. Although I can't really see a way to make this work without having `ty` and `field` be comptime parameters with the current system of how...

cargo doc currently fails when documenting the syntax crate

uhhhhh what? the error gives practically no information lol I'm getting the same error too

cargo doc currently fails when documenting the syntax crate

The only working command is this: ``` cargo doc --workspace --exclude parser --exclude syntax --exclude lexer --no-deps ```

cargo doc currently fails when documenting the syntax crate

I posted an issue to rust-lang/cargo to see if they had any ideas https://github.com/rust-lang/rust/issues/126638

Store some variables in registers instead of always using the stack

I'm gonna start working on this

functions to perform bit reeinterpretation for floating point numbers

Yes, 100%👍