Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collection of issues with potential fixes #151

Open
fuhsnn opened this issue Jan 8, 2025 · 2 comments
Open

Collection of issues with potential fixes #151

fuhsnn opened this issue Jan 8, 2025 · 2 comments

Comments

@fuhsnn
Copy link

fuhsnn commented Jan 8, 2025

I've been keeping a list of issues encountered while working on my fork here, most of them have minimal repro and the fixing commit associated.

To Rui, can't thank you enough for chibicc; it's not an exaggeration to say it reshaped me as a programmer. If you are back working on the project, I'll help all I can.

@rui314
Copy link
Owner

rui314 commented Jan 8, 2025

Nice. I don't have time to work on this project at the moment, but I'm glad to hear that that helped you thrive your programming skills. This is exactly what this project aimed for.

@soldate
Copy link

soldate commented Jan 8, 2025

Hi, chibicc commits are the best way to understand how a compiler works, great job! You two should create a C+ (a smaller version of C++). A lot of people are trying to do this (dlang, carbom, rust, odin, c2, c3, etc) without success, because they abandon the simplicity of c with more and more stuff. We need a new c, not another thing. i guess modules and fat pointer is mandatory to a new c, classes and exceptions is probably a good thing too and manual memory management. Think about it!! thanks you two for the code!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants