[untitled]
6 comments
The readme is very overwhelming but still doesn't tell me anything about the language, and the only file in the example directory is a hello world.
It might be good to expand on that, for those of us that don't remember the original W++ :)
It might be good to expand on that, for those of us that don't remember the original W++ :)
Very interesting idea.
There was a proposal for a similar feature in Go [0], but it was abandoned due to technical infeasibilty.
What exactly are the rules for when a thread is garbage collected in W++?
[0] github.com/golang/go/issues/19702
There was a proposal for a similar feature in Go [0], but it was abandoned due to technical infeasibilty.
What exactly are the rules for when a thread is garbage collected in W++?
[0] github.com/golang/go/issues/19702
Both the code and this submission are obvious LLM slop, exactly like the previous one. It's really concerning that so many people can't tell.
This might be a parody project, but in case it's not:
> No zombie threads
Is this a problem in need of a solution?
> No zombie threads
Is this a problem in need of a solution?
This is slop. Flag and move on.
GC’d environments already have what you’re describing. This is how Java threads work. This is also how Fil-C’s low level zthread abstraction works. In those systems you can join a thread if you want to, but if you don’t, it’ll free its memory anyway.