Error when running vibe.d example application, not sure of the cause.

2016-08-29 Thread e-y-e via Digitalmars-d-learn
I am currently using the following packages on arch linux (parabola [1] to be exact): - DUB version 1.0.0 - LDC version 1.0.0 I create a project with the following command: $ dub init -t vibe.d vibetest Change directories: $ cd vibetest/ And attempt to build and run the project: $ dub

Re: Error when running vibe.d example application, not sure of the cause.

2016-09-01 Thread e-y-e via Digitalmars-d-learn
On Thursday, 1 September 2016 at 09:37:22 UTC, Kagamin wrote: Probably LDC issue https://github.com/ldc-developers/ldc/issues Thank you for your reply. I built LDC (version 1.1.0 beta 2) from source and ran dub using: $ dub run --compiler="~/Downloads/ldc/bin/ldc2" And everything works

Re: Error when running vibe.d example application, not sure of the cause.

2016-08-30 Thread e-y-e via Digitalmars-d-learn
On Monday, 29 August 2016 at 20:32:27 UTC, e-y-e wrote: [...] Does anyone know of anywhere else I can get help with this error? It's a blocker on me using vibe.d, which is quite frustrating.

Re: construct range from tuple?

2016-09-18 Thread e-y-e via Digitalmars-d-learn
On Sunday, 18 September 2016 at 08:06:54 UTC, Lutger wrote: I have a tuple of strings generated at compile time, for example: alias names = AliasSeq!("Alice", "Bob"); How is it possible to construct a range of strings from this, in order to use it at runtime with other range algorithms?

Re: construct range from tuple?

2016-09-18 Thread e-y-e via Digitalmars-d-learn
On Sunday, 18 September 2016 at 09:36:13 UTC, e-y-e wrote: On Sunday, 18 September 2016 at 08:06:54 UTC, Lutger wrote: [...] Use std.range's 'only' function [1], it takes variadic arguments of the same type and constructs a range consisting of them. Example: import std.meta :

Can someone explain to me the design choices for this function definition?

2016-09-22 Thread e-y-e via Digitalmars-d-learn
The function in question is std.algorithm.searching's until [1]. Here are the definitions: Until!(pred, Range, Sentinel) until(alias pred = "a == b", Range, Sentinel) (Range range, Sentinel sentinel, OpenRight openRight = OpenRight.yes) if (!is(Sentinel == OpenRight)); and: Until!(pred,

Re: No trace of cumulativeFold except in the source.

2016-10-23 Thread e-y-e via Digitalmars-d-learn
On Sunday, 23 October 2016 at 10:19:07 UTC, Jonathan M Davis wrote: On Sunday, October 23, 2016 10:10:40 e-y-e via Digitalmars-d-learn wrote: ... Per http://dlang.org/changelog/2.071.0.html 2.071.0 came out at the beginning of April, and 2.072 has been slow in coming, so we've only had

Re: No trace of cumulativeFold except in the source.

2016-10-23 Thread e-y-e via Digitalmars-d-learn
On Sunday, 23 October 2016 at 09:11:08 UTC, Jonathan M Davis wrote: On Sunday, October 23, 2016 07:46:19 e-y-e via Digitalmars-d-learn wrote: ... It's not a bug. It's just too new. You looked at the master branch on github, whereas what you're probably using on your computer is 2.071.2

No trace of cumulativeFold except in the source.

2016-10-23 Thread e-y-e via Digitalmars-d-learn
Recently I needed to use a cumulative sum function, so I looked in phobos' documentation for 'cumulative' but found nothing useful. Then I looked in the forums for it and found nothing useful. But when I searched phobos for it I found cumulativeFold in std.algorithm.iteration:

How to enable SIMD instructions in core.simd

2016-11-19 Thread e-y-e via Digitalmars-d-learn
Found that I was not able to use SIMD as import core.simd : __simd; produces the error: 'module core.simd import '__simd' not found'. Upon further inspection I found that the D_SIMD version is not defined as version (D_SIMD) { pragma(msg, "SIMD Support"); } else { pragma(msg, "No

Re: How to enable SIMD instructions in core.simd

2016-11-19 Thread e-y-e via Digitalmars-d-learn
On Saturday, 19 November 2016 at 13:11:18 UTC, e-y-e wrote: ... Sorry for the noise, I found an LDC issue [1] that explains where I am going wrong (in short, core.simd is not supported in LDC, instead ldc.simd should be used). [1] https://github.com/ldc-developers/ldc/issues/595

Re: [Semi-OT] I don't want to leave this language!

2016-12-05 Thread e-y-e via Digitalmars-d-learn
On Monday, 5 December 2016 at 20:25:00 UTC, Ilya Yaroshenko wrote: Hi e-y-e, The main problem with D for production is its runtime. GC, DRuntime, Phobos is big constraint for real world software production. Good D code should be nothrow, @nogc, and betterC. BetterC means that it must not

[Semi-OT] I don't want to leave this language!

2016-12-05 Thread e-y-e via Digitalmars-d-learn
Currently I have been learning D for about a year and a half. This may seem like a short time, but this is the longest I have stuck with any language. I have only been learning for 4 years and I am currently in university studying first year of computer systems engineering. My main problem