Re: Go 1.5
On Friday, 18 September 2015 at 19:26:27 UTC, Rory wrote: The new GC in Go 1.5 seems interesting. What they say about is certainly interesting. http://blog.golang.org/go15gc "To create a garbage collector for the next decade, we turned to an algorithm from decades ago. Go's new garbage collector is a concurrent, tri-color, mark-sweep collector, an idea first proposed by Dijkstra in 1978." I think this was talked about in general. If I remember correctly the consensus was that 1. D's GC is really primitive (70's style stop the world) and there's a lot of room for improvement 2. However, D has much more important problems currently than a slow GC, e.g. std.allocator, a GC-less phobos, smaller .o files for embedded systems, A better DMD with DDMD, etc. The reason Go has a better GC than D is that Go users have no choice but to use the GC, while D users have a bunch more options.
Go 1.5
The new GC in Go 1.5 seems interesting. What they say about is certainly interesting. http://blog.golang.org/go15gc "To create a garbage collector for the next decade, we turned to an algorithm from decades ago. Go's new garbage collector is a concurrent, tri-color, mark-sweep collector, an idea first proposed by Dijkstra in 1978."
Re: FancyPars
On Friday, 18 September 2015 at 14:24:09 UTC, Stefan Koch wrote: On Friday, 18 September 2015 at 06:13:24 UTC, Rory McGuire wrote: I will open/source the of FancyPars. Great! Looking forward to that. Bastiaan.
Re: FancyPars
On Friday, 18 September 2015 at 06:13:24 UTC, Rory McGuire wrote: I for one will have to delete everything I have on FancyPars and avoid, because I mix work and pleasure all the time, and I have no time in my life for lawyers, life is too short. No worries! I will not sue anyone! of any copyright infringement or the like. I will open/source the of FancyPars. an BNF2FPG translator is possible will not be too useful. (If it does not do really significant work that is quite hard to do without deep-neural networks) That said a first step to translate existing grammars to fpg cam surely be done automatically .
Re: FancyPars
On Friday, 18 September 2015 at 00:30:25 UTC, Ben Boeckel wrote: On Thu, Sep 17, 2015 at 23:40:49 +, Bastiaan Veelo via Digitalmars-d-announce wrote: On Thursday, 17 September 2015 at 20:32:59 UTC, Stefan Koch wrote: > Hmm reading this. No license, is best for now. Take your time, but without a license anyone cloning or forking your repo is in fact violating your copyright. It is not what most people expect on github, and I will have to delete my fork and local clone... By using public repos, you explicitly allow anyone to view and fork your project. There are no implicit rights of *use* of that clone though. You are correct [1], thanks. But I still will have to delete mine, because it contains changes. [1] https://help.github.com/articles/open-source-licensing/#what-happens-if-i-dont-choose-a-license
