D_vs_nim: git repo to compare features of D vs nim and help migrating code bw them. PRs welcome

2018-03-26 Thread timotheecour via Digitalmars-d-announce
D and nim are both very promising. I created this git repo to compare them: https://github.com/timotheecour/D_vs_nim/ Goal: up to date and objective comparison of features between D and nim (to help deciding what language to use), and 1:1 map of features and libraries to help D users learn

Re: D_vs_nim: git repo to compare features of D vs nim and help migrating code bw them. PRs welcome

2018-03-26 Thread meppl via Digitalmars-d-announce
On Tuesday, 27 March 2018 at 01:25:42 UTC, timotheecour wrote: D and nim are both very promising. I created this git repo to compare them: https://github.com/timotheecour/D_vs_nim/ Goal: up to date and objective comparison of features between D and nim (to help deciding what language to use),

Re: Vulkan ErupteD breaking changes and transition strategy

2018-03-26 Thread Anton Fediushin via Digitalmars-d-announce
On Monday, 26 March 2018 at 09:20:13 UTC, ParticlePeter wrote: First of all, don't worry, don't panic, we will figure it out, together ;-). Everything will be alright in the end, and if not, its not the end. On Monday, 26 March 2018 at 07:04:00 UTC, Anton Fediushin wrote: 1. This breaks

Re: Vulkan ErupteD breaking changes and transition strategy

2018-03-26 Thread Anton Fediushin via Digitalmars-d-announce
On Sunday, 25 March 2018 at 22:23:06 UTC, Peter Particle wrote: ErupteD [0] is deprecated (one of its major modules). The project content is supposed to be replaced completely. Current state was copied into ErupteD-V1 [1] (without deprecation message), neither ErupteD nor ErupteD-V1 will be

Re: The final form of the keyboard = ShionKeys

2018-03-26 Thread shion via Digitalmars-d-announce
On Saturday, 24 March 2018 at 04:06:12 UTC, barry wrote: On Saturday, 24 March 2018 at 00:51:22 UTC, shion wrote: Github erased me, without any omens / notice, no reply. So, ShionKeys/, I disappeared on gihub. You have been deleted. I'd call that a bad omen right there. Maybe Github saw the

Re: Vulkan ErupteD breaking changes and transition strategy

2018-03-26 Thread Anton Fediushin via Digitalmars-d-announce
On Monday, 26 March 2018 at 07:51:31 UTC, Seb wrote: On Monday, 26 March 2018 at 07:04:00 UTC, Anton Fediushin wrote: This is a *bad* idea and you shouldn't do that. Just increase MAJOR version and start from there: 2.0.0 - Changing how binding works, Vulkan v1.0.69 2.1.0 - Vulkan 1.0.70

Re: Vulkan ErupteD breaking changes and transition strategy

2018-03-26 Thread Seb via Digitalmars-d-announce
On Monday, 26 March 2018 at 09:04:20 UTC, Anton Fediushin wrote: On Monday, 26 March 2018 at 07:51:31 UTC, Seb wrote: On Monday, 26 March 2018 at 07:04:00 UTC, Anton Fediushin wrote: This is a *bad* idea and you shouldn't do that. Just increase MAJOR version and start from there: 2.0.0 -

Re: Vulkan ErupteD breaking changes and transition strategy

2018-03-26 Thread Seb via Digitalmars-d-announce
On Monday, 26 March 2018 at 07:04:00 UTC, Anton Fediushin wrote: This is a *bad* idea and you shouldn't do that. Just increase MAJOR version and start from there: 2.0.0 - Changing how binding works, Vulkan v1.0.69 2.1.0 - Vulkan 1.0.70 ...And so on. This way semver is followed and you don't

Re: Vulkan ErupteD breaking changes and transition strategy

2018-03-26 Thread ParticlePeter via Digitalmars-d-announce
First of all, don't worry, don't panic, we will figure it out, together ;-). Everything will be alright in the end, and if not, its not the end. On Monday, 26 March 2018 at 07:04:00 UTC, Anton Fediushin wrote: 1. This breaks semver. You shouldn't just use Vulkan's versions. If you release

Re: Vulkan ErupteD breaking changes and transition strategy

2018-03-26 Thread Anton Fediushin via Digitalmars-d-announce
On Monday, 26 March 2018 at 11:13:03 UTC, ParticlePeter wrote: I strongly believe that the generator can be made fail safe, so that the produced binding is error free. I will elaborate a little more about the greater plan at the bottom, I just didn't think that anyone is interested in it.

Re: Vulkan ErupteD breaking changes and transition strategy

2018-03-26 Thread ParticlePeter via Digitalmars-d-announce
On Monday, 26 March 2018 at 09:50:16 UTC, Anton Fediushin wrote: On Monday, 26 March 2018 at 09:20:13 UTC, ParticlePeter wrote: First of all, don't worry, don't panic, we will figure it out, together ;-). Everything will be alright in the end, and if not, its not the end. [snip] The bug then

Re: Why think unit tests should be in their own source code hierarchy instead of side-by-side

2018-03-26 Thread Atila Neves via Digitalmars-d-announce
On Friday, 23 March 2018 at 14:54:57 UTC, Steven Schveighoffer wrote: On 3/22/18 6:59 AM, Atila Neves wrote: Blog post: https://atilanevesoncode.wordpress.com/ Atila It's simple. Unittests in imported modules should not be visible. They should be compiled as if -unittest was not passed.

Announcing the DConf 2018 Hackathon Pass

2018-03-26 Thread Mike Parker via Digitalmars-d-announce
In the vicinity of Munich May 2-5 but can't make it to the full four days of DConf 2018? Now you can come join us for the Hackathon on Saturday, May 5 with a Hackathon Pass. Those who sign up will be able to spend the day with the rest of us talking about, hacking on, and learning D. And we

Re: Vulkan ErupteD breaking changes and transition strategy

2018-03-26 Thread ParticlePeter via Digitalmars-d-announce
On Monday, 26 March 2018 at 12:22:25 UTC, Anton Fediushin wrote: On Monday, 26 March 2018 at 11:13:03 UTC, ParticlePeter wrote: [snip] Here I was hoping for a little more attentive reading, the bugfix (if any bugs happen in the end) for v1.1.70 would be v1.1.71 (as in "point seven ONE")