3 ms·
Or just use zig
by pyrolistical 4y ago
Or just use zig
- andrewflnr 4y agoIs this going to be the meme, now?
- gpderetta 4y agoYes! At least till the end of the week then we will be looking for the next glorious replacement.
- com2kid 4y agoCould have said "use any language that has built in control over allocation strategies". Sad that C doesn't. Ada does, Rust does, Zig does, plenty of other languages do, C does not, which is hilariously odd considering how often C has to run in places that don't have a heap.
- andrewflnr 4y agoYeah, they could have said that. It would have been smarter. They didn't, though. I occasionally see this where I respond to what someone says, and get a reply along the lines of "they could have said this other thing", like that's relevant. It baffles me every time. They didn't say your smarter thing, they said their silly thing. I guess projecting your smarter ideas on someone else's comment is one of the better mistakes you can make...
- throwawaymaths 4y agoYou should probably add some context for this to be meaningful. Could be: - zig stdlib functions take an allocator as a parameter for dynamic memory datatypes and you can supply a static allocator - in the near future it will be possible to link c libraries against a modular libc written in zig, so you will be able to use c code that uses malloc in a statically allocation-only context. The second one should be exciting for embedded c developers because with a little work zig could be worked into a c toolchain so that with otherwise almost no zig code you can use a c library, or, ambitiously a c++ library, that assumes malloc in an embedded application
- mhh__ 4y agoYeah just rewrite the whole project bro