On Saturday, 19 February 2022 at 17:33:07 UTC, matheus wrote:
By the way English isn't my first language but I think there is
a small typo:
"In D, such nuances are fewer, for header files are not
required."
I think it's missing the word "example":
"In D, such nuances are fewer, for example
On Thursday, 10 February 2022 at 08:06:23 UTC, Mathias LANG wrote:
make `auto` peel the outermost qualifier level inside functions.
Shouldn't do that for class references. Otherwise seems fine.
On Monday, 24 January 2022 at 23:33:29 UTC, Walter Bright wrote:
The phrase "How bad really is the D ecosystem?" only asks a
question, but people tend to interpret such sentences as "D's
ecosystem is really bad". What works better is:
"How good really is the D ecosystem?"
Your suggested
On Tuesday, 25 January 2022 at 00:08:54 UTC, H. S. Teoh wrote:
This may work for x86, but does it work for other platforms? If
not, it won't fly on LDC/GDC.
I don't think there's anything wrong with d having its own ABI.
But, I checked arm and riscv: both of their c calling conventions
have
On Friday, 21 January 2022 at 12:55:58 UTC, ag0aep6g wrote:
I still believe it should be fairly simple:
https://forum.dlang.org/post/ofc0lj$2u4h$1...@digitalmars.com
There is a simpler solution: put the context pointer in rax.
This is currently a caller-saved register, so there is no
On Wednesday, 12 January 2022 at 16:17:02 UTC, H. S. Teoh wrote:
Depends on what kind of games, I guess. If you're writing a
60fps real-time raytraced 3D FPS running at 2048x1152
resolution, then *perhaps* you might not want a GC killing your
framerate every so often.
Resolution is down to
On Wednesday, 12 January 2022 at 15:41:03 UTC, Adam D Ruppe wrote:
idk about hf trading
Per hearsay, some is c++, some is java, frequently it is
fpga-assisted. Certainly, gc is not unheard of in that domain.
On Friday, 7 January 2022 at 21:41:55 UTC, Walter Bright wrote:
: 89 F8 mov EAX,EDI
Feature request: octal.
On Wednesday, 5 January 2022 at 13:43:19 UTC, Robert Schadek
wrote:
I would guess with my library your manual effort, at least for
range primitives, is down to
```sh
dub add range_primitives_helper
```
Indeed. This is for when you want to write your own constraints.
On Wednesday, 5 January 2022 at 12:32:10 UTC, Elronnd wrote:
There's a trick I came up with, that I've been meaning to post
about
There is another thing I should mention: the isInputRange I
showed is not strictly equivalent to the standard version,
because SFIAE. So a dispatch stage is
Cool project!
The mechanism you use is very special-purpose, in that you have
to write a lot of specific code to get such nice output. There's
a trick I came up with, that I've been meaning to post about,
which gives slightly less nice output, but requires no manual
effort and is completely
On Saturday, 16 October 2021 at 01:08:11 UTC, max haughton wrote:
issues with references being held and confusing the GC, also.
A reminder (if one were needed) that one can still have memory
leaks with GC :)
On Thursday, 27 May 2021 at 01:04:37 UTC, Iain Buclaw wrote:
2. The promise of dynamically generating D bindings from C
headers never really materialized. Actual work of adding a GCC
compiler switch to dump D code was [completed to around 95% of
what was
Maybe the wrong place to bring it up, but: any chance this will
be merged into core.sys.windows?
(_start is the wasm's equivalent of _Dmain)
Not really; _start (in libc) is used on Linux too, which sets
up the C runtime, then calls C main, which calls druntime's
_d_run_main which in turn calls _Dmain.
Small correction: _start generally calls __libc_start_main() or
similar, with the
15 matches
Mail list logo
