News for hackers. Stuff that matters.
Re:What's new in purely functional data structures since Oka... by legulere on Monday February 08, 2016 @07:33AM (#11057726)
> Since Swift is implemented in C++, no doubt that's why it's not a reality in that new language either.

The language the compiler is implemented in doesn't matter, so I guess you mean that it's not possible because Swift is too heavily influenced by C++? I don't think that this is really the case, it's more influenced by Objective-C

[deleted]
Re:What's new in purely functional data structures since Oka... by scott_s on Monday February 08, 2016 @10:04AM (#11058432)
The language used to implement the compiler and runtime system for a new language has no impact on what is possible in the new language. If the implementation language does not natively support something you want in the new language, you can just implement that yourself, and it is then available to the new language.

For example, C does not natively support garbage collection, but Python certainly does. The most popular Python implementation is implemented in C.

Re:What's new in purely functional data structures since Oka... by hellofunk on Monday February 08, 2016 @10:09AM (#11058472)
Thanks for pointing that out. I'm not a language or compiler engineer so my sight wasn't big enough. I tend to think of a new language as a gigantic library sitting on top of another language, and just assumed that if the base language can't handle something like a persistent data structure, then the new language would struggle with that as well.
Re:What's new in purely functional data structures since Oka... by dkersten on Monday February 08, 2016 @10:57AM (#11058773)
Only a very small handful of languages are actually implemented like this.

Its worth also pointing out that some languages that compile to C, still support features that C does not (for example, Chicken Scheme compiles to C and supports both garbage collection and continuations, neither of which C supports natively).

Re:What's new in purely functional data structures since Oka... by masklinn on Monday February 08, 2016 @11:36AM (#11059072)
> for example, Chicken Scheme compiles to C and supports both garbage collection and continuations, neither of which C supports natively

And GHC still allows compiling Haskell (lazy, functional, garbage-collected) via C (eager, procedural, manually managed).

Re:What's new in purely functional data structures since Oka... by kazagistar on Monday February 08, 2016 @10:41AM (#11058670)
That is almost never an accurate way to think about it.
Re:What's new in purely functional data structures since Oka... by autoreleasepool on Monday February 08, 2016 @09:39PM (#11062698)
> I tend to think of a new language as a gigantic library sitting on top of another language

That's a bad default assumption

Re:What's new in purely functional data structures since Oka... by thinkpad20 on Monday February 08, 2016 @10:05AM (#11058440)
> it is about what is possible in the language based on how it is implemented (which is C++)

What is possible to express in a language is determined by its specification, not its implementation. Of course, it's up to the implementor to correctly adhere to the spec, but this is also independent of language choice. It's certainly possible, and has been done, to implement a language with GC, TCO, lazy evaluation, purity, etc etc, in a language like C++ which has none of those things. For example, the nix language, which has all of those things except TCO (which it certainly could have in theory) is implemented in C++.