Viewing profile — anqurvanillapy

Cool, and the paper mentioned in the document "Dependent Types for Low-Level Programming" [1] is such a gem. [1]: https://people.eecs.berkeley.edu/~necula/Papers/deputy-esop0...

I love your gradual approach pretty much. It sounds like gradual typing but not just the typing part. I used to make many tools with libclang Python bindings to automate some chore…

> Build embedded or core OS code with it. things that do MMIO, DMA interactions, low level IO in kernel code or firmware (more embedded). I have a friend currently writing a GC in …

> Offer real and significant benefits. Yeah! The criterion is just there like you said. > Do you have an opinion on the dotnet version of generics? I'm not familiar with dotnet lan…

> On the other hand I think we are in a local maxima with programming languages and type systems. I think I gotcha. Oh no. > But I haven't finished fleshing it out and proving the …

Love all the ideas here. I found it might be possible to tackle "strict aliasing" and "pointer provenance" with a type system and I would head down to it early. The approach might …

> But the only thing that really took off was effort to change things at the very base level rather than patch issues. Exactly, that's the most important takeaway I got from all th…

Notable approaches to compatibility with C might be: 1) LLVM, like Rust and Zig did (Zig stopped using it in 2023), since LLVM IR is good for being compatible and optimizing. 2) Ot…

I love this idea so much. I got stuck at how to tackle "new language doesn't compile with a standard C compiler" for many times, but my solution is much worse than yours: Like LuaJ…

Oh I heard about it and oops just hate myself for forgetting it. And the first sentence [1] of its pointer type introduction, exactly says everything I said here... > [...] greates…

Woah I enjoyed the read a lot. I also learned that in LLVM IR, they have the implicit null checks [1] to replace the guard with just a signal handler, so it won't hurt the branch p…

Thanks for the mention! I heard about Carbon years ago but I'm happy this time I could dig it further for insights now. It's pretty fun to think about "Carbon to C++ is Kotlin to J…

That's true! Sorry that I didn't much clarify the "pain" though: It's quite like the experience of using parser combinator in Rust, where you could happily define the grammar and t…

Thanks sooo much! I would definitely do it!

> Imagine writing large games in your language. You don’t. Read the features I listed. One ends up with a C alternative frontend (Cfront, if you love bad jokes) including type syst…

Exactly the kind of thoughts and insights I need from more of the users. Thank you for pointing out many concerns. > Headers. C++20 modules are left unstable and unused in major co…

> There are approaches e.g. Zig. Yes! Zig has done a great job on many C-related stuff, e.g. they've already made it possible to cross-compile C/C++ projects with Zig toolchain yea…

And then? https://github.com/anqurvanillapy/TinyLean

Ah that should be good for source-level compatibility. But I'm thinking about extending existing codebase that crosses between the kernel and user space, e.g. DPDK, SPDK, FUSE, ker…

> We seem to have the same desire for a “cleaned up C.” That's so great! But sad that no enough ideas and argument came up here. :'( > How metaprogramming would work? When it comes…

Hi I'm Anqur, a senior software engineer with different backgrounds where development in C was often an important part of my work. E.g. 1) Game: A Chinese/Vietnam game with C/C++ f…

No, this very paragraph is even highlighted in many major social media in China. The public opinions are oriented that people should be wise about products of Huawei.