4 ms·
These issues should / could all be addressed - if you're in Discord already, which it sounds like you probably are, feel free to talk about each point. The C2V
by ylluminate 5y ago
These issues should / could all be addressed - if you're in Discord already, which it sounds like you probably are, feel free to talk about each point. The C2V source IS in fact, already available to many folks (v devs specifically, of which there are many).
- vlang1dot0 5y agoThe last time I asked about how the memory management would work, the conversation was quickly shut down by a vlang dev (not Alex) who grilled on me on why I wanted to know how the language worked. I've seen this same reaction to other newcomers who dare to ask reasonable questions instead of simply drinking the Kool aide.
- ylluminate 5y agoStrange, I'll mention it. There have been a lot of crazy trolls so a few folks are a bit thin on the patience front - especially a few who are crazy hard at work all the time on the language. I do have sympathy for them and they're great folks if you just try to understand the history and their own context a bit.
- vlang1dot0 5y agoI think it would be more productive to direct the attention to https://github.com/vlang/v/issues/1247 https://github.com/vlang/v/issues/1247 which catalogues a number of issues with the proposed approach and yet hasn't had any activity in 9 months.
- super_flanker 5y agoDitto same experience, I asked if somebody could explain me the memory model of V; and all of sudden hell broke loose. I was asked why do I need to know how memory model worked, are you a troll, if you don't contribute to the lang you're not welcome here. Never asked a second question again.
- vlang1dot0 5y agoYep. Very telling when no one on the server can explain it and anyone who asks is silenced.