On Thursday, 17 December 2020 at 22:06:00 UTC, SealabJaster wrote:
...
Well, at least I understand why the context pointer exists now.
If you were to add a `pragma(msg, __FUNCTION__)` into either of
the templated functions, you'd get the following output.
```
example.C.doShizz!(a).doShizz
e
On Friday, 18 December 2020 at 19:15:16 UTC, Daren Scot Wilson
wrote:
On Wednesday, 16 December 2020 at 07:45:50 UTC, Ferhat
Kurtulmuş wrote:
On Wednesday, 16 December 2020 at 07:40:45 UTC, Ferhat
Kurtulmuş wrote:
This may be not your issue, but I could manage it to work by
adding this line:
On Wednesday, 16 December 2020 at 07:45:50 UTC, Ferhat Kurtulmuş
wrote:
On Wednesday, 16 December 2020 at 07:40:45 UTC, Ferhat
Kurtulmuş wrote:
This may be not your issue, but I could manage it to work by
adding this line:
subPackage "examples/myproject"
to the dub.sdl of the beamui. I simp
On Wednesday, 16 December 2020 at 07:40:45 UTC, Ferhat Kurtulmuş
wrote:
On Wednesday, 16 December 2020 at 07:02:11 UTC, Daren Scot
Wilson wrote:
Trying out the beamui GUI package, obtained by git clone from
github. The "basic" example builds and runs.
I'm working on an Arch Linux machine with
On Friday, 18 December 2020 at 16:23:20 UTC, Adam D. Ruppe wrote:
On Friday, 18 December 2020 at 16:18:12 UTC, Dave P. wrote:
Is the proper solution to change the struct definition to:
yeah that's the best option right now
A bit of a pain when porting, but alright.
I find the setting flo
Two differents types; Foo type and pointer type. Need function
overload foe each or just use ref and avoid pointer.
On Friday, 18 December 2020 at 13:00:45 UTC, Severin Teona wrote:
Hi guys!
Do you know how can I compile D code using LDC with the
following gcc flags?
* -msingle-pic-base
* -mpic-register=r9
* -mno-pic-data-is-text-relative.
As far as I know, there are no equivalents in D for these. Is
is o
On Friday, 18 December 2020 at 16:18:12 UTC, Dave P. wrote:
Is the proper solution to change the struct definition to:
yeah that's the best option right now
I find the setting floats to nan pretty bizarre.
yeah i wrote about it here not long ago
http://dpldocs.info/this-week-in-d/Blog.Post
I got burned by behavior of struct initialization I didn’t
anticipate last night.
Consider a struct:
struct Foo {
float x, y, z;
int a, b, c;
}
My source C code was initializing it by doing something like:
Foo f = {.y = 3}
Which uses the C behavior that all the other fields will be s
Hi guys!
Do you know how can I compile D code using LDC with the following
gcc flags?
* -msingle-pic-base
* -mpic-register=r9
* -mno-pic-data-is-text-relative.
As far as I know, there are no equivalents in D for these. Is is
ok to use the -Xcc flag?
Thank you!
On 12/17/20 5:57 PM, H. S. Teoh wrote:
On a side note, though, I find this idiosyncratic behaviour annoying
when all I really want is to use an array as, e.g., a backing for a
stack. For those cases, I ignore array capacity and keep a slice over
the entire allocated storage, including elements t
On 12/17/20 1:10 PM, IGotD- wrote:
On Thursday, 17 December 2020 at 17:46:59 UTC, Steven Schveighoffer wrote:
This isn’t correct. Can you post the code that led you to believe this?
-Steve
Sure.
import std.algorithm;
import std.typecons;
import std.stdio;
struct Buffer
{
this(size_t
The manual often doesn't show the full potential of traits on the
first sight or what they are really good for. But there are also
all-day scenarios where I would just be happy for a quick lookup.
For example, to assign a value to a class property which may have
setter-overloads, I'm using a p
13 matches
Mail list logo
