3 ms·
It depends who you are creating the language for. If the language is for the computer so that it can compile in a single pass then maybe forward declarations ar
by mmphosis 4y ago
It depends who you are creating the language for. If the language is for the computer so that it can compile in a single pass then maybe forward declarations are a way.
When I write code, I don't want it cluttered with boilerplate and dependency declarations. And when I read code, I don't want it cluttered with boilerplate and dependency declarations. The problem is not your language, the problem is packages and the dependency hell they will create. There are no deal-breakers, just compromises.
- ghoward 4y agoI do want this language to be for people, but having keywords definable by the user bumps up against people on both ends. I think you are right that there may not really be dealbreakers, just compromises. I'm trying to think of ways to reduce the forward declarations without needing more than one pass. As of right now, I have ideas for not needing forward declarations for types and for variables. But mutually recursive functions still do need forward declarations. I don't think there will be many of those, and I'm wondering if that is good enough. What do you think?