nacaclanga
nacaclanga
The main differences between C++ build systems and these other build systems boils down to two points: a) Standardized. A single build system is heavily pushed by the compiler builders...
> Supposedly cargo build plans were supposed to describe the build rules sufficiently that e.g. Meson could then merge cargo's build rules into a build.ninja file and track build edges...
Might be interesting for this discussion: https://odin.handmade.network/blog/p/2994-on_the_aesthetics_of_the_syntax_of_declarations. That said, I do not think, that a syntax involving "let" is beneficial. If we would go for this, the keyword let should...
> The main concern about adding socket addresses to core seems to be: > > > If the socketaddr types aren't identical across platforms, I don't think we want them...
Hi, yes I was using a lasy_static RwCell global for the reciver, which isn't a very flexible approach. I now reworked my commit in such a way that the the...
`extends` works IMO better, when you only allow a single class to be specified here, while `:` works better with a "bounded by mixins point of view. https://github.com/carbon-language/carbon-lang/blob/trunk/docs/design/generics/overview.md#interfaces descibes interfaces...
Maybe we add a "/// cbindgen header: xyz.h" attribute for modules. When called in a "--multiple" mode, cbindgen would generate a header file for each module with this annotation only...
cbindgen does not generate any new rust code. It also does not generate any C function definitions. It merely generates a header file listing exposed functions and types. This means...
One other way to translate macros would be to use some sort of custom preprocessor: Within the C code, we replace, (after checking if a macro forms a valid expression)...
For some users, it might also be of interest to see, whether a grammar will also fullfill the LALR restrictions. In case this is easy to check, one could consider...