Re: [GSoC] Precise GC
On Wednesday, 7 September 2016 at 02:15:30 UTC, Dsby wrote: On Friday, 2 September 2016 at 03:25:33 UTC, Jeremy DeHaan wrote: Hi everyone, I know I'm super late to the party for this, and sorry for that. While my work on the precise GC didn't go as planned, it is closer than it was to be getting merged. [...] In Mac 32 bit. the test is not pass. I didn't have a mac to test this on at the time. I currently have some things ordered so that I can see what is actually going on and fix this.
mysql-native v0.1.6
Another small update, v0.1.6, to fix this: Linker error when using dub to import *just* vibe-d:core, but not all of vibe.d. At least once code.dlang.org notices the new tag.
Re: [GSoC] Precise GC
On Saturday, 3 September 2016 at 12:22:25 UTC, thedeemon wrote: On Friday, 2 September 2016 at 14:55:26 UTC, jmh530 wrote: Anyway, with @safe unions, my thinking is that it would mean that the garbage collector can be made precise in @safe code in a way that it can't in @system code (assuming unions with pointers aren't snuck in through @trusted). GC (and runtime in general) has no idea what code is safe and what code is system. GC works with data at run-time. All @safe-related stuff is about code (not data!) and happens at compile-time. They are completely orthogonal and independent, as I understand. This is correct, but when designing a GC – in particular, a precise GC –, having the compiler emit additional helpful metadata to binaries is always an option worth considering. — David
Re: [OT] LLVM 3.9 released - you can try the release already with LDC!
On Tuesday, 6 September 2016 at 10:51:16 UTC, eugene wrote: On Tuesday, 6 September 2016 at 09:42:11 UTC, Lodovico Giaretta wrote: There are lot of projects using LLVM [1]. The fact that LDC if often cited in the release notes means that it's one of the best. This is free advertisement, as the LLVM release notes are read by PL people that may not know D. The fact that LDC is recognized as one of the most important LLVM projects also means that the LLVM folks will try to help the LDC folks when needed. [1] http://llvm.org/ProjectsWithLLVM/ i dont think counting each time when ldc and d are mentioned in llvm community will help ldc and d to become popular))) News ticker often refer to the LLVM release notes. E.g. the Heise news ticker (http://www.heise.de/) always reports about a new LLVM release. But I never succeded to place a new LDC release into the ticker. It's simply a good way to more people and get some advertising. With every new LDC release I inform LLVM Weekly (http://llvmweekly.org/), too, which is a widely read news letter. From one of these source, news about LDC spread to other sites like phoronix (http://phoronix.com/). Maybe counting of each reference is a bit childish (but fun). The real question is: What do YOU do to advocate D? Regards, Kai
Re: Battle-plan for CTFE
On Thursday, 8 September 2016 at 13:11:23 UTC, Stefan Koch wrote: On Thursday, 8 September 2016 at 10:44:55 UTC, Stefan Koch wrote: compiling parts of phobos does no longer crash the new engine. However it still produces incorrect byte-code :) I think I have taken care of the incorrect bytecode. It was not an issue with the engine itself but rather with the way I plugged it in. The new engine is not supposed being called if the old one has already started to interpret the function, because the two do not and should not share state. I found more incorrect code. this time it's located more deeply in the engine. I am investigating the cause. It seems to be related closures somehow.
Re: workspace-d 2.7.2 & code-d 0.10.14
On Thursday, 8 September 2016 at 06:50:58 UTC, Suliman wrote: It's possible to integrate workspace-d with Sublime? Yes, as long as you can start a process and read its output & write to its input in binary, you can do it. Message format is available here: https://github.com/Pure-D/workspace-d Documentation of all modules is available here: https://workspaced.webfreak.org/
mysql-native v0.1.5
Tagged a new release of mysql-native: A client driver for MySQL/MariaDB written natively in D from scratch via the published protocol specs, with no dependency on the C MySQL client library. Supports either Phobos or Vide.d sockets (works with or without Vibe.d). Despite the seemingly low version number, this library is used in real-world projects by various people and has been around (with various maintainers and contributors) since Steve Teale's original release in 2011. In this version: - New: #73: Integration testing via travis-ci. (@Abscissa) - New: Started this changelog. (@Abscissa) - Fixed: #20: Contract failure in consume!string (@Marenz) - Fixed: #50: bindParameters example was wrong (@Abscissa) - Fixed: #67: Fix unittest for escape (@Marenz) - Fixed: #70: Check for errors where we expect the greeting packet (@Marenz) - Fixed: #78: Use vibe-d sub package dependency and a more current version (@s-ludwig) - Fixed: #79: Dub fetch all vibe-d dependencies, even if there is no reason (@s-ludwig) Full changelog: https://github.com/mysql-d/mysql-native/blob/master/CHANGELOG.md Future direction: Priorities need to be a published API documentation and some good docs, plus continue addressing the existing issues/PRs. Github Homepage: https://github.com/mysql-d/mysql-native On DUB: http://code.dlang.org/packages/mysql-native
Re: Battle-plan for CTFE
On Thursday, 8 September 2016 at 14:48:25 UTC, Rory McGuire wrote: On Thu, Sep 8, 2016 at 3:11 PM, Stefan Koch via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote: On Thursday, 8 September 2016 at 10:44:55 UTC, Stefan Koch wrote: compiling parts of phobos does no longer crash the new engine. However it still produces incorrect byte-code :) I think I have taken care of the incorrect bytecode. It was not an issue with the engine itself but rather with the way I plugged it in. The new engine is not supposed being called if the old one has already started to interpret the function, because the two do not and should not share state. !! Does this mean I can start testing new ctfe and only some of my CT will be faster? You can start yes. However it is very limited right now I would expect it to slow you down by a little bit.
Re: Battle-plan for CTFE
On Thu, Sep 8, 2016 at 3:11 PM, Stefan Koch via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote: > On Thursday, 8 September 2016 at 10:44:55 UTC, Stefan Koch wrote: > >> compiling parts of phobos does no longer crash the new engine. >> However it still produces incorrect byte-code :) >> > > I think I have taken care of the incorrect bytecode. > It was not an issue with the engine itself but rather with the way I > plugged it in. > The new engine is not supposed being called if the old one has already > started to interpret the function, because the two do not and should not > share state. > > !! Does this mean I can start testing new ctfe and only some of my CT will be faster?
Re: Battle-plan for CTFE
On Thursday, 8 September 2016 at 10:44:55 UTC, Stefan Koch wrote: compiling parts of phobos does no longer crash the new engine. However it still produces incorrect byte-code :) I think I have taken care of the incorrect bytecode. It was not an issue with the engine itself but rather with the way I plugged it in. The new engine is not supposed being called if the old one has already started to interpret the function, because the two do not and should not share state.
Re: Battle-plan for CTFE
compiling parts of phobos does no longer crash the new engine. However it still produces incorrect byte-code :)
Re: workspace-d 2.7.2 & code-d 0.10.14
On Thu, Sep 8, 2016 at 8:50 AM, Suliman via Digitalmars-d-announce <
digitalmars-d-announce@puremagic.com> wrote:
> On Wednesday, 7 September 2016 at 18:27:41 UTC, WebFreak001 wrote:
>
>> On Wednesday, 7 September 2016 at 18:14:29 UTC, Suliman wrote:
>>
>>> You could look my PC with TeamViewer
>>>
>>
>> Ok problem fixed. The config was invalid, it needs to look like this:
>>
>> {
>> "d.stdlibPath": [
>> "C:\\D\\dmd2\\src\\phobos",
>> "C:\\D\\dmd2\\src\\druntime\\import"
>> ]
>> }
>>
>> Just forgot these braces {} to make it valid json
>>
>
> It's possible to integrate workspace-d with Sublime?
>
+1
