News for hackers. Stuff that matters.
Re:Nim compiler — Pascal source code by k__ on Sunday November 29, 2020 @07:08AM (#25244688)
Nice.

I'm still dreaming of a world where Rust had Nim syntax.

Re:Nim compiler — Pascal source code by arc619 on Sunday November 29, 2020 @08:05AM (#25244919)
Why not just use Nim? The language is rapidly converging on an ownership model similar to rust anyway and has better metaprogramming, more compile targets and a high development velocity (plus faster compile times).

Rust has a bigger ecosystem of course, but Nim's is pretty decent and you can use C, C++ and JS libs natively for anything else.

Re:Nim compiler — Pascal source code by fwsgonzo on Sunday November 29, 2020 @08:17AM (#25244960)
We really need a simpler language that has the same ownership model. I like Nim because I can compile it without threading support, and for RISC-V (albeit 64-bit, wish it had 32-bit support too..).

Overall, I like it, but I could not justify using it in an enterprise setting without knowing that the direction of the language is going towards what is now the established minimum safety, which is borrow checking and no UB.

Re:Nim compiler — Pascal source code by gameswithgo on Sunday November 29, 2020 @10:31AM (#25245654)
if you have borrow checking, you are going to inherit a lot of complexity in order to deal with the limitations it imposes. you could be simpler than rust, for sure, but bot as simple as say C or Go.

Zig might be a language you are interested in. Simple like C with sensible ways of dealing with UB and bounds checking, as well as options instead of Nulls.

Re:Nim compiler — Pascal source code by planetis on Sunday November 29, 2020 @01:42PM (#25246990)
Zig is interesting but still very immature. Its memory model is manual management thus has no advantages over rust or nim. So it's marketed as better C (not any more than that).
Re:Nim compiler — Pascal source code by pizza234 on Sunday November 29, 2020 @11:44AM (#25246212)
> We really need a simpler language that has the same ownership model

Can you mention which part of the Rust language you found complicated (in real world), excluding the ownership/memory management area (which includes: bck, lifetimes, smart pointers, traits related to synchronization)?

I read a lot of comments about Rust's complexity, and while nobody doubts the complexity of the ownership/memory management, there's a very common lack of details when it comes to the rest of the language.

Re:Nim compiler — Pascal source code by pjmlp on Sunday November 29, 2020 @01:42PM (#25246991)
The rest of the language is just fine if you are used to the ML language family, maybe that is the issue for those coming from more mainstream languages.
Re:Nim compiler — Pascal source code by zinclozenge on Sunday November 29, 2020 @12:37PM (#25246565)
No algebraic datatypes + pattern matching, yes I'm aware of libraries that implement it via metaprogramming, but that's not good enough for me.
Re:Nim compiler — Pascal source code by arc619 on Sunday November 29, 2020 @02:24PM (#25247316)
> No algebraic datatypes

Not sure what you mean there, there's product types with tuples and objects, and sum types as object variants.

> Pattern matching

Eh, I mean it's just sugar over a case statement.

  let
    num = 5
    str = case num
      of 1: "One!"
      of 2, 3, 5, 7, 11: "This is a prime"
      of 13..19: "A teen"
      else: "Unknown"  # Compile error if all cases arent covered.
As you say there's libraries that let you deconstruct and partially match more complex types if you need that. Being able to create things like pattern matching, async, and novel multithreading runtimes as a library in Nim shows how powerful (and useful) the metaprogramming is.

Enums in Rust are more interesting, but again nothing you can't do with an object variant.

Re:Nim compiler — Pascal source code by kevin_thibedeau on Sunday November 29, 2020 @01:19PM (#25246835)
Try using Rust without any macros.
Re:Nim compiler — Pascal source code by simias on Sunday November 29, 2020 @11:34AM (#25246148)
Nim is nice but "better metaprogramming" is going to be very contentious I think. "Different metaprogramming" for sure, but the rest is a matter of preference frankly.

Nim macros are a lot nicer than Rust's, but Rust's trait system is very powerful and expressive. Sure, you can do something like that with Nim's macros, but you can't expect that all third party code is going to play nice.

That's the problem with the macro approach: it's great because it's ultra-flexible, but it also sucks because it's ultra-flexible. Everybody ends up doing their own little DSL that fits their use case or their personal taste, and it adds friction at the interfaces.

Re:Nim compiler — Pascal source code by nikki93 on Sunday November 29, 2020 @01:29PM (#25246916)
Is this based on having used Nim in practice in projects and observing the code of many Nim projects and collecting data / insights; or without having used Nim and on speculation / general thoughts about macros / DSLs (or somewhere along the spectrum)? Just so it's clear how to contextualize.

Because having tried to explore these questions by studying Nim projects, going through a book and working on a game engine in it the past months; I've found that ufcs+overloading covers the static traits scenario, and it feels like the runtime traits object scenario is better self-rolled (I don't really want the compiler impl'ing vtables underneath me, save deciding to reuse a static dispatch feature for a dynamic one; if I want a struct of func ptrs I will make a struct of func ptrs.) at least for my usage. Various Nim code I come across is usually pretty readable, and I don't need to invent macros willy nilly.

ufcs feels more elegant than needing to decide whether to namespace a function inside a struct or not (or which one), which is what most langs (including Rust) seem to do.

Re:Nim compiler — Pascal source code by planetis on Sunday November 29, 2020 @01:46PM (#25247016)
There is no "friction" with macros, sure lot's of packages implement their own utility macros but most can be hidden under ordinary procs. Macros CAN be called like ORDINARY procs, check syntactic sugar module [1], though not all macros are designed this way. Unless we are talking about public DSLs. But I don't really understand what's the problem with them.

[1] https://nim-lang.github.io/Nim/sugar.html

Re:Nim compiler — Pascal source code by planetis on Sunday November 29, 2020 @01:52PM (#25247065)
Also macros do not capture their caller AST! They operate on the code passed to them. Another important point that removes any friction. This way nesting macros works with no problem, they're expanded in order. (I can think even more reasons why your argument is unbased, like "hygienic" identifiers, operating on AST level versus ugly string concats, etc but whatever.)
Re:Nim compiler — Pascal source code by Xevi on Sunday November 29, 2020 @09:56AM (#25245426)
I don't know much about Rust, and even less about Nim, but does this mean that Nim will have the same safety guarantees that Rust has? Also, can you really just add something like that down the line and ensure that the whole ecosystem works correctly? I was under the impression that Rust's strength was that it's been designed from the start to use an ownership model.
Re:Nim compiler — Pascal source code by beagle3 on Sunday November 29, 2020 @03:54PM (#25247988)
Nim’s arc/orc mode (introduced in 1.4 and likely to become default in 2.0) does borrow checking but does nit enforce it in the same way Rust does: instead, you’ll get a compiler warning “i can’t just borrow here, so I am making a copy” which you can prevent by making your type uncopyable (which will make this an error). The semantics are not equivalent to rust, but they are similar.

Nim stops race conditions by controlling data passage among threads (disallowing shared data between threads, in general) and always has.

I am not familiar enough with Rust to say that everything rust can do and assure is indeed covered in Nim; however, plain Nim without using the escape hatches (which like Rust unsafe code, exist for those times you must use them) is safe.

Re:Nim compiler — Pascal source code by Xevi on Sunday November 29, 2020 @04:07PM (#25248101)
That's awesome. I'm currently studying Rust, but I'm looking forward to giving Nim a try in a year or two. I really like the syntax, and if it can offer the same safety and performance as Rust, then I see a bright future for it.
Re:Nim compiler — Pascal source code by k__ on Sunday November 29, 2020 @08:20AM (#25244979)
"The language is rapidly converging on an ownership model similar to rust "

Nice.

Do you have more resources on that?

Also, does Nim have a WASM target?

Re:Nim compiler — Pascal source code by sp33der89 on Sunday November 29, 2020 @09:00AM (#25245123)
Re:Nim compiler — Pascal source code by planetis on Sunday November 29, 2020 @02:12PM (#25247205)
Latest presentation is https://www.youtube.com/watch?v=zPlBZkWvuug It has updated information.
Re:Nim compiler — Pascal source code by nikki93 on Sunday November 29, 2020 @03:36PM (#25247858)
Re: WASM -- https://github.com/nikki93/ng-public -- Public repo for a game side project I've been working on that does Nim -> C/C++ -> WASM (native desktop also works, iOS probably works (have used the same build system for C++ iOS before) and Android can be made to work). One of the modules involved wraps entt which is a template-heavy C++ library and not many languages can actually wrap with just a cdecl-y ffi layer.

Re: borrow checking: https://nim-lang.org/docs/manual_experimental.html#view-type... It's still pretty early and also IME the mix of arc (which is determinstic) with manually managed memory (esp. through some data structure that manages entity data like entt) has been pretty nice.

Re:Nim compiler — Pascal source code by atombender on Sunday November 29, 2020 @11:54AM (#25246286)
Nim is apparently getting support for owned pointers [1]. There's a proposal [2]. The proposal PR has since been closed, but it's apparently still being worked on.

[1] https://nim-lang.org/araq/ownedrefs.html

[2] https://github.com/nim-lang/RFCs/issues/144

Re:Nim compiler — Pascal source code by planetis on Sunday November 29, 2020 @02:16PM (#25247246)
I had played with and really liked "owned". However there was design issues with it and that feature was forgotten.
Re:Nim compiler — Pascal source code by beagle3 on Sunday November 29, 2020 @03:57PM (#25248004)
Most of those semantics are now tracked automatically without needing annotation in arc/orc.
Re:Nim compiler — Pascal source code by gameswithgo on Sunday November 29, 2020 @07:42AM (#25244833)
If you are hoping for the lack of curly braces in particular, there is F#, which is sort of Rust with the minor matter of having a garbage collector, and inefficient iterators.