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 run
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.
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 now,
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?
F
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 : AliasSeq
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, R
On Thursday, 22 September 2016 at 21:41:38 UTC, Lodovico Giaretta
wrote:
2. Why is openRight not a Flag type?
It may be that until is quite old, predating the extensive
usage of Flag, and maybe also the extensive use of compile-time
flags.
Ok, I suspected this might be the case. I might wor
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:
https://github.c
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
comp
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 onl
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 SIM
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
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 is
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 re
14 matches
Mail list logo