Mirror of forum.nim-lang.org

3399 :: [Presentation-Python-Nim] A new option for optimizing inner loops Z. D. Smith

[2017-12-06T15:22:05+01:00]

bvld (orginal) [2017-12-06T15:22:05+01:00] view original

<https://www.youtube.com/watch?v=IVgNVJdizHg>

Udiknedormin (orginal) [2017-12-06T23:51:52+01:00] view original

It suggests the new direction the Nim is to be heading to (according to Araq's blog post), i.e. turning away from GC, it would more or less ruin things for the guy talking. :-/

mratsim (orginal) [2017-12-07T13:30:28+01:00] view original

I think the goal is to make the core types (seq, strings) non-dependent on the GC so that Nim is easier to use from other languages that also have their GC or to use in constrained environment (no heap, embedded devices, real-time/deterministic constraints).

As far as i know the GC will always be a (supported) option.

Udiknedormin (orginal) [2017-12-08T18:46:09+01:00] view original

@mratsim Well, it seemed to me the current idea is to push the GC aside so that Nim will become scope-based "by default" with optional GC just where it's needed. Thanks for the explanation though.