On Monday, 11 June 2018 at 19:05:21 UTC, Basile B. wrote:
On Monday, 11 June 2018 at 16:37:05 UTC, Basile B. wrote:
Russel Winder, "Shove" and finally myself, have encountered a
strange linker error with almost always the same symbols
related to a template instance...
See:
-
https://forum.d
On Wednesday, 13 June 2018 at 06:10:26 UTC, Cym13 wrote:
That's very nice! Out of curiosity, what was the reason to
avoid a conventional stack? Or was it a consequence more than a
design decision? (If you've explained it before, feel free to
just throw the old post at me)
It was an initial
On Wednesday, 13 June 2018 at 05:57:31 UTC, Stefan Koch wrote:
Good day ladies and gentleman,
it is my distinct please to announce that a new feature just
landed in newCTFE.
!!! DELEGATES !!!
Nice!
On Wednesday, 13 June 2018 at 05:57:31 UTC, Stefan Koch wrote:
Good day ladies and gentleman,
it is my distinct please to announce that a new feature just
landed in newCTFE.
!!! DELEGATES !!!
this means the following code will now work:
int square_of_x_plus_x(int x) pure
{
int passThroug
Good day ladies and gentleman,
it is my distinct please to announce that a new feature just
landed in newCTFE.
!!! DELEGATES !!!
this means the following code will now work:
int square_of_x_plus_x(int x) pure
{
int passThrough(int y) pure
{
assert(x == y);
int y2 = x;
On Saturday, 9 June 2018 at 02:38:14 UTC, SonicFreak94 wrote:
On Saturday, 9 June 2018 at 02:17:18 UTC, Adam D. Ruppe wrote:
On Saturday, 9 June 2018 at 02:13:00 UTC, Walter Bright wrote:
But it was never enforced, meaning that suddenly enforcing it
is just going to break code left and right.
On 6/12/2018 7:31 PM, makedgreatagain wrote:
Thanks for all you help, the betteC is really useful and handy.
That's great to hear!
On Tuesday, 12 June 2018 at 18:41:57 UTC, Walter Bright wrote:
On 6/12/2018 5:13 AM, makedgreatagain wrote:
extern(C) int main(string[] args){
Need to declare main() like those C people do:
extern (C) int main(int argc, char** argv){
Thanks for all you help, the betteC is really useful an
On Wednesday, 13 June 2018 at 02:18:55 UTC, makedgreatagain wrote:
On Tuesday, 12 June 2018 at 04:23:51 UTC, Joakim wrote:
On Monday, 11 June 2018 at 04:02:15 UTC, Joakim wrote:
On Monday, 11 June 2018 at 02:58:28 UTC, makedgreatagain
wrote:
On Thursday, 7 June 2018 at 14:12:15 UTC, Joakim wro
On Tuesday, 12 June 2018 at 04:23:51 UTC, Joakim wrote:
On Monday, 11 June 2018 at 04:02:15 UTC, Joakim wrote:
On Monday, 11 June 2018 at 02:58:28 UTC, makedgreatagain wrote:
On Thursday, 7 June 2018 at 14:12:15 UTC, Joakim wrote:
[...]
Thanks for your help.
The side thing is betterC change
On 6/12/18 4:19 PM, bauss wrote:
On Tuesday, 12 June 2018 at 17:24:31 UTC, Basile B. wrote:
I don't know if more doc is necessary. The warning is at its right
place IMO.
If they're reserved the compiler should honestly throw a warning at the
very least.
People should have to read through th
On Tuesday, 12 June 2018 at 17:24:31 UTC, Basile B. wrote:
On Tuesday, 12 June 2018 at 15:42:50 UTC, Bauss wrote:
On Tuesday, 12 June 2018 at 14:37:19 UTC, ag0aep6g wrote:
On Tuesday, 12 June 2018 at 13:40:45 UTC, bauss wrote:
See the following: https://run.dlang.io/is/uQ21PH
(I have tried wi
On 6/12/2018 5:13 AM, makedgreatagain wrote:
extern(C) int main(string[] args){
Need to declare main() like those C people do:
extern (C) int main(int argc, char** argv){
On Tuesday, 12 June 2018 at 15:39:52 UTC, Zoadian wrote:
On Tuesday, 12 June 2018 at 15:21:49 UTC, Jacob Shtokolov wrote:
On Tuesday, 12 June 2018 at 14:33:57 UTC, Steven Schveighoffer
wrote:
[...]
Thank you Steve!
Then I'll try to fire a bug report and propose my own solution
to this probl
On Tuesday, 12 June 2018 at 15:42:50 UTC, Bauss wrote:
On Tuesday, 12 June 2018 at 14:37:19 UTC, ag0aep6g wrote:
On Tuesday, 12 June 2018 at 13:40:45 UTC, bauss wrote:
See the following: https://run.dlang.io/is/uQ21PH
(I have tried with allMembers too.)
It's like it won't pick up the member t
Or use C malloc.
We really should provide better tools to create arrays using C
malloc (for those who want them). Like a betterC toolkit.
-Steve
Indeed, i´m creating my own "toolkit" for betterC stuff like
alloc!Type(length); (much safer than malloc!) and other utilities
:)
On Tuesday, 12 June 2018 at 14:37:19 UTC, ag0aep6g wrote:
On Tuesday, 12 June 2018 at 13:40:45 UTC, bauss wrote:
See the following: https://run.dlang.io/is/uQ21PH
(I have tried with allMembers too.)
It's like it won't pick up the member that is added using a
mixin at line 22.
```
mixin("uby
On Tuesday, 12 June 2018 at 15:21:49 UTC, Jacob Shtokolov wrote:
On Tuesday, 12 June 2018 at 14:33:57 UTC, Steven Schveighoffer
wrote:
[...]
Thank you Steve!
Then I'll try to fire a bug report and propose my own solution
to this problem.
Probably there is no need to track down the non-object
On Tuesday, 12 June 2018 at 14:33:57 UTC, Steven Schveighoffer
wrote:
On 6/12/18 9:04 AM, Jacob Shtokolov wrote:
[...]
I'll respond to say that I don't know a lot of people who use
signals and slots. It's a very old part of Phobos, and I think
a lot of people here aren't familiar with it.
On 6/12/18 10:18 AM, SrMordred wrote:
On Tuesday, 12 June 2018 at 12:29:17 UTC, rikki cattermole wrote:
(...)
this line:
byte[] data = [0, 1];
is an dynamic array allocated with GC.
But if you declare as a static array like
byte[2] data = [0, 1];
than its not GC allocated.
Or use C mall
On Tuesday, 12 June 2018 at 13:40:45 UTC, bauss wrote:
See the following: https://run.dlang.io/is/uQ21PH
(I have tried with allMembers too.)
It's like it won't pick up the member that is added using a
mixin at line 22.
```
mixin("ubyte[" ~ to!string(__PADDING_SIZE__) ~ "] __PADDING__"
~ mem
On 6/12/18 9:04 AM, Jacob Shtokolov wrote:
On Thursday, 7 June 2018 at 12:56:55 UTC, Jacob Shtokolov wrote:
Hello,
I'd like to start a discussion about the standard std.signals library.
[...]
5 days passed and no one answered 😒
I'll respond to say that I don't know a lot of people who use
On Tuesday, 12 June 2018 at 12:29:17 UTC, rikki cattermole wrote:
(...)
this line:
byte[] data = [0, 1];
is an dynamic array allocated with GC.
But if you declare as a static array like
byte[2] data = [0, 1];
than its not GC allocated.
On Monday, 11 June 2018 at 15:41:57 UTC, Steven Schveighoffer
wrote:
On 4/11/18 3:13 PM, bauss wrote:
On Wednesday, 11 April 2018 at 17:58:25 UTC, Jonathan M Davis
wrote:
On Sunday, April 08, 2018 13:00:02 bauss via Digitalmars-d
wrote:
[...]
I don't know. It could be argued either way. I th
On Tuesday, 12 June 2018 at 13:40:45 UTC, bauss wrote:
See the following: https://run.dlang.io/is/uQ21PH
Note: Look at the comments in the code.
See the following: https://run.dlang.io/is/uQ21PH
(I have tried with allMembers too.)
It's like it won't pick up the member that is added using a mixin
at line 22.
```
mixin("ubyte[" ~ to!string(__PADDING_SIZE__) ~ "] __PADDING__" ~
member ~ ";");
```
As you can see if you take sizeof fro
On Tuesday, 12 June 2018 at 11:10:30 UTC, Per Nordlöw wrote:
I just discovered
https://github.com/ShigekiKarita/grain
which seems like a very ambitious and active project for making
dynamic neural networks run on the GPU using D in front of mir
and CUDA.
Are there any long-term goals around
On Thursday, 7 June 2018 at 12:56:55 UTC, Jacob Shtokolov wrote:
Hello,
I'd like to start a discussion about the standard std.signals
library.
[...]
5 days passed and no one answered 😒
Maybe the guys who are contributing to DRuntime could answer: is
that possible to attach GC dispose even
On 13/06/2018 12:13 AM, makedgreatagain wrote:
this very simple code can not build with betterC
void test(byte[] x){
}
extern(C) int main(string[] args){
byte[] data = [0, 1];
test(data);
return 0;
}
Well yes, dynamic arrays require the GC and hence TypeInfo. Slices
don't,
this very simple code can not build with betterC
void test(byte[] x){
}
extern(C) int main(string[] args){
byte[] data = [0, 1];
test(data);
return 0;
}
On Tuesday, 6 March 2018 at 10:17:42 UTC, Walter Bright wrote:
On 3/6/2018 1:58 AM, Jonathan M Davis wrote:
[...]
The entire point of making assert a core language feature was
so that the compiler could take advantage of it to generate
better code. It's been like that for D since day 1. It h
On Tuesday, 12 June 2018 at 04:23:51 UTC, Joakim wrote:
On Monday, 11 June 2018 at 04:02:15 UTC, Joakim wrote:
On Monday, 11 June 2018 at 02:58:28 UTC, makedgreatagain wrote:
On Thursday, 7 June 2018 at 14:12:15 UTC, Joakim wrote:
[...]
Thanks for your help.
The side thing is betterC change
I just discovered
https://github.com/ShigekiKarita/grain
which seems like a very ambitious and active project for making
dynamic neural networks run on the GPU using D in front of mir
and CUDA.
Are there any long-term goals around this project except for the
title?
It would great if someo
33 matches
Mail list logo
