The Goose Programming Language

Re:The Goose Programming Language by weinzierl on Saturday October 24, 2026 @05:22PM (#50225450)

I guess my question is if you can trigger UB in regular Goose and if you can, would it be considered a bug. I realize that this doesn't necessarily have a simple yes or no answer but I still think it'd help to know if Goose is more on the C++ side or the Rust side.

The complete omission of UB in the README could be one of two things. Either that the topic is not important or that it is considered a given and not worth mentioning.

[ Parent | on HN ]

Re:The Goose Programming Language by vanderZwan on Saturday October 24, 2026 @05:36PM (#50225595)

Hmm, well the benchmarks always use an explicit "faster than idiomatic C/C++ and safe Rust". Similarly it also notes that in theory you could write equally fast C/C++ (since Goose compiles to C), but it would be an unreadable, unsafe mess.

Note also the fact that e.g. array indexing has bounds checks without escape hatches for the programmer, but the compiler can elide quite a few of them, and the language has tools to help the programmer write code that is guaranteed to be check-free.

I think that suggests the ambition is to compete with Rust in the domain of combining safety with not compromising on performance.

[ Parent | on HN ]

Re:The Goose Programming Language by jibalt on Sunday October 25, 2026 @02:34AM (#50228900)

Goose has no undefined behavior.

[ Parent | on HN ]