3 ms·

Rain Programming Language by nikeedev

• deleted 2y ago
  [deleted]
• brudgers 2y ago
  Thanks for sharing your work. Please post direct links to HN not redirections. Your work might make a good candidate for ShowHN if it meets the guidelines. Thanks again.
  • nikeedev 2y ago
    Thank you so much! I will look into ShowHN. nikeedev
• rad_gruchalski 2y ago
  Little bit more about the language: https://github.com/nikeedev/rain-lang/blob/main/language_syntax.md https://github.com/nikeedev/rain-lang/blob/main/language_syn.... I like that syntax.
  • konaraddi 2y ago
    The `once` is a cool idea, looks like it expresses “this may be mutated many times but used at most once”
  • Minor49er 2y ago
    Semicolons appear to end statements, but are also optional, given the examples. Is this just because JavaScript allows it?
• nine_k 2y ago
  Since it's in the very early stages, that's what I'm missing here: - The rationale. What is the problem, and why a new language solves the problem better than the existing ones. Are there killer features? - The main motifs of the language. There is a bunch of known ways to build a language; which are followed, and what are new ideas, if any? (Packaging well-known ideas well is totally OK.) In particular, approaches to mutability, purity, type system, classes/objects, async, parallel, safety (lifetimes, UB, etc), resource control (GC, RC, RTTI, etc). - Modularity within the language, and interaction with third-party libraries (e.g. FFI). - The target(s): native code generation, a VM, WASM, JS, transpiling through C, etc. After that, specific language features and syntax niceties become much easier to reason about.