Write your plan here, and let's take a rendez-vous next year, to check those plans !!

On Monday, 2 January 2017 at 15:16:31 UTC, Basile B. wrote:
> Write your plan here, and let's take a rendez-vous next year, to check those plans !!

I don't really plan for a whole year but I want to make a game in D and write basically everything I do for my servers, work, etc. in D

On Monday, 2 January 2017 at 15:16:31 UTC, Basile B. wrote:
> Write your plan here, and let's take a rendez-vous next year, to check those plans !!

I plan to improve dmd.
After newCTFE is merged, I will work on the template-subsystem.
As well as on the general infrastructure in dmd.

On Monday, 2 January 2017 at 15:30:34 UTC, Stefan Koch wrote:
> On Monday, 2 January 2017 at 15:16:31 UTC, Basile B. wrote:
>> Write your plan here, and let's take a rendez-vous next year, to check those plans !!
>
> I plan to improve dmd.
> After newCTFE is merged, I will work on the template-subsystem.
> As well as on the general infrastructure in dmd.

Thank you!

On Monday, 2 January 2017 at 15:30:34 UTC, Stefan Koch wrote:
> I plan to improve dmd.
> After newCTFE is merged, I will work on the template-subsystem.

Does that include improved template restriction diagnostics upon failing instantiations :)

> As well as on the general infrastructure in dmd.

Sounds great!

On Monday, 2 January 2017 at 15:16:31 UTC, Basile B. wrote:
> Write your plan here, and let's take a rendez-vous next year, to check those plans !!

Enable non-copyable (r-value) ranges to be passed to range-based algorithms that require a single reference to the source range. My motivation for this is to enable non-copyable values, typically containers, to be passed by move into a specific range I currently call `UniqueRange`. `UniqueRange`, being in turn non-copyable, should then be passed Phobos' higher-order algorithms, typically `map`, `filter`, `reduce` etc. `UniqueRange` is similar to Rusts' `IntoIterator`. In order for this happen both the compiler and Phobos needs be adjusted in a non-breaking way.

Here's a sample implementation of this idea that compiles and tests out correctly with a branch of Phobos (link provided below).

https://github.com/nordlow/phobos-next/blob/master/src/unique_range.d

being a wrapper for

https://github.com/nordlow/phobos-next/blob/master/src/array_ex.d

The first thing is to improve the compiler so that it always moves the last reference (in scope X) of a variable passed by value into scope X (typically as a function parameter or foreach aggregate). More specifically this lowers to calling `doCopyOrMove()` on the DMD node of that last reference. The challenge is to find *which* node(s) this applies to.

This will enable D to compete with Rust's iterator flexibility by enabling range-based D algorithms to be safely and efficiently combined with containers (both copyable and non-copyable).

To kickstart this I need help by the DMD developers on figuring out how to fix DMD so that move semantics kicks in all places where it should (as described above). After DMD has been fixed, I will happily implement the rest.

Andrei has already approved this improvement as seen here

https://github.com/dlang/phobos/pull/4971

On Monday, 2 January 2017 at 17:10:03 UTC, Nordlöw wrote:
> Here's a sample implementation of this idea that compiles and tests out correctly with a branch of Phobos (link provided below).

Correction `UniqueRange` can be used today together with the array containers defined in array_ex.d together with the adjusted Phobos-algorithms in unique_range.d

> https://github.com/nordlow/phobos-next/blob/master/src/unique_range.d
>
> being a wrapper for
>
> https://github.com/nordlow/phobos-next/blob/master/src/array_ex.d

On Monday, 2 January 2017 at 15:16:31 UTC, Basile B. wrote:
> Write your plan here

Not a lot, actually. I do have more dpldocs.info improvements coming, a few more changes to my terminal emulator, but not much else.

My D stuff is no longer something I write much directly, it is now support for support tasks - I write helper programs for me, and do lib stuff or applications to help my helper programs, but I'm pretty productive right now as-is, so not as much pressure to push anymore.

On Monday, 2 January 2017 at 15:16:31 UTC, Basile B. wrote:
> Write your plan here, and let's take a rendez-vous next year, to check those plans !!

* get back into reviewing PRs more often

* use vibe.d in a shipped project

* write more D articles/tutorials (possibly on vibe.d)

On Monday, 2 January 2017 at 15:16:31 UTC, Basile B. wrote:
> Write your plan here, and let's take a rendez-vous next year, to check those plans !!

My own plan is still related to runtime-info based serialization. I know that people  inject the bloat each time they want serialization:

write object: template bloat
read object: template bloat
object inspector: template bloat
object binding: template bloat

What I'd like to show is that whatever is the context, you don't need the template bloat. Simply thanks to the runtime type info.