-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Incorrect C code generation when trying to echo a Lock variable #12855
Comments
Why close? The issue is still there |
It's been several months and there was no feedback, I figured an issue wasn't necessary. |
@3n-k1 that's not how it works in open-source in general - it just means that nobody worked on the issue yet, but as long as the bug is still there it should be open |
I understand how FOSS works. Now, I would prefer if you didn't mention me again as I would prefer not to receive notifications for this. |
It's been over half a year, and I get a bad taste in my mouth every time I see this. I'm closing this, and I will be blocking anyone who responds or re-opens; I really don't care if that makes me an ass. Y'all have a minimal example and all the information necessary for this, feel free to open a new issue with a copy-paste of the initial issue I posted here. This is me officially leaving the Nim community. So long, and thanks for all the fish. |
I'm okay with getting blocked by you - but really, "leaving" the community because of INCORRECT Nim code not compiling (even if it compiles it'll crash at best since you didn't initialize the lock, and for printing you can just try to use repr or cast to a pointer and repr) is not okay. Also this is open source, not some software you paid for, so you maybe should've tried fixing it yourself before? :) |
Just brigading so I can get my promised block. I certainly would not like you to use anything I contribute on. |
@Yardanico I'm leaving the community because Araq has treated me like shit numerous times, but thanks for playing. |
The fact you need to bitch and moan about someone not wanting to be treated like a fucking piece of garbage just confirms this community is fucking garbage. |
@beef331 Even if I did want to use any of your trash, it would be a bit difficult since you apparently can't bring yourself to write more than two sentences in a readme, assuming you write anything at all. Nice website by the way, I really enjoy the gif of your superman64 clone playing as the site's background. You wanna get shitty? Let's fuckin' go, kid. At least I actually contributed to Nim before Araq treated me like shit, unlike you. Araq, be careful who you treat like garbage, you may lose one of your shitty niche language's biggest evangelists. |
Am I ranting now? Sure the fuck am. I thought you'd all be able to be fucking adults about this, but I guess fucking not. |
Bad C code is generated with the following Nim code:
Example
Current Output
Expected Output
Compiler either compiles properly or errors before C code gen
Possible Solution
$
for the Lock typeAdditional Information
Linux localhost.localdomain 5.3.11-300.fc31.x86_64 #1 SMP Tue Nov 12 19:08:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: