How can I initialize my two dimensional array?
When I try to run the code below I get the error:
Error: non-constant expression ["user":[cast(Capability)0],
"administrator":[cast(Capability)1]]
Code:
enum Capability {
self,
administer
}
alias Capabilities =
On Monday, 8 June 2020 at 06:13:36 UTC, mw wrote:
Hi,
I have this program:
import std.stdio;
void f(ref int[] arr) {
arr ~= 3;
}
void main() {
int[][] arrs;
int[] arr;
foreach (i; 0 .. 3) {
On Monday, 8 June 2020 at 06:37:18 UTC, tirithen wrote:
How can I initialize my two dimensional array?
When I try to run the code below I get the error:
Error: non-constant expression ["user":[cast(Capability)0],
"administrator":[cast(Capability)1]]
Code:
enum Capability {
On Monday, 8 June 2020 at 07:35:12 UTC, adnan338 wrote:
Hi, as far as I understand, the `this` template parameter
includes constness qualifiers as seen in
https://ddili.org/ders/d.en/templates_more.html
To apply this I have this following struct:
module bst;
struct Tree(T) {
T item;
Hi, as far as I understand, the `this` template parameter
includes constness qualifiers as seen in
https://ddili.org/ders/d.en/templates_more.html
To apply this I have this following struct:
module bst;
struct Tree(T) {
T item;
Tree!T* parent, left, right;
this(T item) {
On Monday, 8 June 2020 at 07:35:12 UTC, adnan338 wrote:
Self* searchTree(this Self)(auto in ref T item) const {
if ( is null)
return null;
if (this.item == item)
return
return (this.item < item) ?
this.right.searchTree(item) :
Hi,
I have this program:
import std.stdio;
void f(ref int[] arr) {
arr ~= 3;
}
void main() {
int[][] arrs;
int[] arr;
foreach (i; 0 .. 3) {
arr = new int[0];
arrs ~= arr; //(a)
On Monday, 8 June 2020 at 06:42:44 UTC, Simen Kjærås wrote:
Arrays (technically, slices) in D are essentially this struct:
struct Array(T) {
T* ptr;
size_t length;
// operator overloads
}
So when you have int[][], each element of the outer array is an
Array!int. These, as simple
On Monday, 8 June 2020 at 02:55:25 UTC, jmh530 wrote:
```
...
template foo(string f) {
mixin("alias foo = .foo!(" ~ f ~ ");");
}
...
```
Out of curiosity what does the "." in front of `foo` mean? I've
seen that in some D code on the compiler in GitHub and have no
idea what it does. I
On 08.06.20 16:27, data pulverizer wrote:
Out of curiosity what does the "." in front of `foo` mean? I've seen
that in some D code on the compiler in GitHub and have no idea what it
does. I tried Googling it to no avail. It doesn't have anything to do
with UFCS does it?
On Monday, 8 June 2020 at 02:55:25 UTC, jmh530 wrote:
In the code below, foo!fabs compiles without issue, but
foo!"fabs" does not because the import is not available in the
string mixin.
Why do you even want foo!"fabs"? Usually when I see people having
this problem it is actually a
On 08.06.20 16:41, Jan Hönig wrote:
On Sunday, 7 June 2020 at 00:45:37 UTC, Ali Çehreli wrote:
[...]
writeln(q{
void foo() {
}
});
What is the name of this `q` thing?
How do i find it? Are there any recent tutorials on it?
https://dlang.org/spec/lex.html#token_strings
On Sunday, 7 June 2020 at 00:45:37 UTC, Ali Çehreli wrote:
On 6/6/20 5:03 PM, FunkyD wrote:> On Saturday, 6 June 2020 at
09:57:36 UTC, Jan Hönig wrote:
> D is pretty good for meta-programming. For certain other
things it is
> terrible.
I am glad I don't know enough about other technologies to
On Monday, 8 June 2020 at 14:27:26 UTC, data pulverizer wrote:
[snip]
Out of curiosity what does the "." in front of `foo` mean? I've
seen that in some D code on the compiler in GitHub and have no
idea what it does. I tried Googling it to no avail. It doesn't
have anything to do with UFCS
On Sunday, 7 June 2020 at 00:45:37 UTC, Ali Çehreli wrote:
dmd -mixin= ...
thanks for the tip!
writeln(q{
void foo() {
}
});
What is the name of this `q` thing?
How do i find it? Are there any recent tutorials on it?
On 08.06.20 16:45, ag0aep6g wrote:
On 08.06.20 16:41, Jan Hönig wrote:
On Sunday, 7 June 2020 at 00:45:37 UTC, Ali Çehreli wrote:
[...]
writeln(q{
void foo() {
}
});
What is the name of this `q` thing?
How do i find it? Are there any recent tutorials on it?
On Monday, 8 June 2020 at 14:41:55 UTC, Jan Hönig wrote:
What is the name of this `q` thing?
It is just a string that looks like code.
On Monday, 8 June 2020 at 09:08:40 UTC, adnan338 wrote:
On Monday, 8 June 2020 at 08:10:19 UTC, Simen Kjærås wrote:
On Monday, 8 June 2020 at 07:35:12 UTC, adnan338 wrote:
Self* searchTree(this Self)(auto in ref T item) const {
if ( is null)
return null;
if
On Monday, 8 June 2020 at 06:52:36 UTC, mw wrote:
On Monday, 8 June 2020 at 06:42:44 UTC, Simen Kjærås wrote:
Arrays (technically, slices) in D are essentially this struct:
struct Array(T) {
T* ptr;
size_t length;
// operator overloads
}
So when you have int[][], each element of
On Monday, 8 June 2020 at 08:10:19 UTC, Simen Kjærås wrote:
On Monday, 8 June 2020 at 07:35:12 UTC, adnan338 wrote:
Self* searchTree(this Self)(auto in ref T item) const {
if ( is null)
return null;
if (this.item == item)
return
return
On Monday, 8 June 2020 at 10:23:24 UTC, jmh530 wrote:
On Monday, 8 June 2020 at 04:13:08 UTC, Mike Parker wrote:
[snip]
The problem isn't the mixin. It's the template. Templates take
the scope of their declaration, not their instantiation. So
the mixin is getting the template's scope.
On Monday, 8 June 2020 at 10:28:39 UTC, Paul Backus wrote:
[snip]
Thanks for that suggestion. That works for me.
Unfortunately, it's probably not worth the extra effort though,
versus doing foo!fabs in my case.
On Monday, 8 June 2020 at 04:13:08 UTC, Mike Parker wrote:
[snip]
The problem isn't the mixin. It's the template. Templates take
the scope of their declaration, not their instantiation. So the
mixin is getting the template's scope.
Anyway, this appears to work:
`double z =
On Monday, 8 June 2020 at 06:13:36 UTC, mw wrote:
what I really want in (a) is append `ref arr` and output [[3],
[3], [3]], i.e. the real `arr` be appended instead of its copy.
I tried to change arrs' decl to:
(ref (int[]))[] arrs; // the intended semantics I want
1) I'm wondering how
On Monday, 8 June 2020 at 12:20:46 UTC, Adam D. Ruppe wrote:
[snip]
Why do you even want foo!"fabs"? Usually when I see people
having this problem it is actually a misunderstanding of what
is possible with the foo!fabs style - which is better in
basically every way and can be used in most
On Monday, 8 June 2020 at 10:41:53 UTC, jmh530 wrote:
On Monday, 8 June 2020 at 10:28:39 UTC, Paul Backus wrote:
[snip]
Thanks for that suggestion. That works for me.
Unfortunately, it's probably not worth the extra effort though,
versus doing foo!fabs in my case.
If they are all from
Hi,
I'm trying to build this package:
https://code.dlang.org/packages/fixed
however, the compiler error out:
ldc2-1.21.0-linux-x86_64/bin/../import/std/math.d(5783,39):
Error: llroundl cannot be interpreted at compile time, because it
has no available source code
Looks like it does some
On Monday, 8 June 2020 at 18:08:57 UTC, mw wrote:
2) even it does so, but why such simple function as lroundl
cannot be CTFE-ed?
Because, as the error message states, there's no source for it :)
std.math calls into C math library.
On Monday, 8 June 2020 at 18:43:58 UTC, Stanislav Blinov wrote:
On Monday, 8 June 2020 at 18:08:57 UTC, mw wrote:
2) even it does so, but why such simple function as lroundl
cannot be CTFE-ed?
Because, as the error message states, there's no source for it
:) std.math calls into C math
On Sunday, 7 June 2020 at 16:54:48 UTC, Paul Backus wrote:
On Sunday, 7 June 2020 at 16:26:17 UTC, Andre Pany wrote:
On Sunday, 7 June 2020 at 15:37:27 UTC, Paul Backus wrote:
On Sunday, 7 June 2020 at 12:52:12 UTC, Andre Pany wrote:
I am not sure but $DUB is a variable which could be used
On Monday, 8 June 2020 at 17:55:24 UTC, Andre Pany wrote:
I had a second look on the descriptions and from a non native
speaker view it sounds correct.
But you are right from a native speaker view the wording might
be incorrect.
If you have time, could you check the wording and make a
On Monday, 8 June 2020 at 18:38:17 UTC, Paul Backus wrote:
On Monday, 8 June 2020 at 17:55:24 UTC, Andre Pany wrote:
I had a second look on the descriptions and from a non native
speaker view it sounds correct.
But you are right from a native speaker view the wording might
be incorrect.
If
On 6/8/20 2:08 PM, mw wrote:
Hi,
I'm trying to build this package:
https://code.dlang.org/packages/fixed
however, the compiler error out:
ldc2-1.21.0-linux-x86_64/bin/../import/std/math.d(5783,39): Error:
llroundl cannot be interpreted at compile time, because it has no
available source
On 6/8/20 11:11 AM, jmh530 wrote:
On Monday, 8 June 2020 at 14:27:26 UTC, data pulverizer wrote:
[snip]
Out of curiosity what does the "." in front of `foo` mean? I've seen
that in some D code on the compiler in GitHub and have no idea what it
does. I tried Googling it to no avail. It
On Monday, 8 June 2020 at 16:02:02 UTC, Steven Schveighoffer
wrote:
On 6/8/20 11:11 AM, jmh530 wrote:
On Monday, 8 June 2020 at 14:27:26 UTC, data pulverizer wrote:
[snip]
Out of curiosity what does the "." in front of `foo` mean?
[snip]
ag0aep6g provided the link to it [snip]
The dot
On 6/8/20 2:53 PM, mw wrote:
And with a symbol-to-c-func table, it should be able to just call that C
func.
Consider that the libc available to the compiler might not be the same
as the libc for the target (e.g. cross compilation).
Not just that, but this opens the compiler up to a huge
On Monday, 8 June 2020 at 19:05:45 UTC, Steven Schveighoffer
wrote:
On 6/8/20 2:53 PM, mw wrote:
And with a symbol-to-c-func table, it should be able to just
call that C func.
Consider that the libc available to the compiler might not be
the same as the libc for the target (e.g. cross
37 matches
Mail list logo
