On Monday, 22 January 2024 at 23:28:40 UTC, Jonathan M Davis
wrote:
Of course, ultimately, different programmers have different
preferences, and none of us are going to be happy about
everything in any language.
It's not only about preferences. The feature is inconsistent with
how
On Tuesday, 3 October 2023 at 19:03:00 UTC, Walter Bright wrote:
$0.
true
On Monday, 2 October 2023 at 17:28:19 UTC, Mike Parker wrote:
https://www.reddit.com/r/programming/comments/16y2h36/crafting_selfevident_code_in_dlang/
'enum { Yes, No }; is just an automatic “no hire” decision'
'No hire' for language designers who design sum types to be
implicitly
On Saturday, 30 September 2023 at 12:40:29 UTC, Guillaume Piolat
wrote:
When is it useful?
You can use it to troll Jonathan Blow.
On Friday, 7 July 2023 at 10:45:33 UTC, Guillaume Piolat wrote:
I don't remember people from outside the community being
impressed by alias this.
We have the right to backtrack on bad ideas instead of keeping
them forever.
I don't know why anybody should be impressed, but Zig and Jai,
the
On Monday, 1 May 2023 at 14:03:51 UTC, bachmeier wrote:
```
value.type = STRING;
```
IRL people would use namespacing prefixes or actual namespaces
anyway, so your example would look more like
```
value.type = VALUE_TYPE_STRING;
```
On Thursday, 2 February 2023 at 22:46:51 UTC, Ali Çehreli wrote:
https://forum.dlang.org/thread/qwixdanceeupdefyq...@forum.dlang.org
I still agree with myself :) in that discussion here:
https://forum.dlang.org/post/tlqcjq$usk$1...@digitalmars.com
BTW, check out another case of D
On Monday, 26 September 2022 at 04:40:02 UTC, Mike Parker wrote:
You may have seen [the long discussion about the deprecation of
binary
literals(https://forum.dlang.org/thread/vphguaninxedxopjk...@forum.dlang.org).
A few hours ago, Walter and I recorded a second conversation
for our YouTube
On Saturday, 6 August 2022 at 08:29:19 UTC, Walter Bright wrote:
On 8/5/2022 9:43 AM, Max Samukha wrote:
Both "123." and "123.E123" is valid C. For some reason, D only
copied the former.
It's to support UFCS (Universal Function Call Syntax).
UFCS could still be supported with the exception
On Friday, 5 August 2022 at 15:44:10 UTC, Steven Schveighoffer
wrote:
On 8/5/22 11:36 AM, Rumbu wrote:
float z = 85886696878585969769557975866955695.E0; //integer
overflow, I don't see any int
That's an integer, which is trying to call a UFCS function
named `E0`. Did you mean to include the
On Tuesday, 8 June 2021 at 11:35:39 UTC, Iain Buclaw wrote:
Testing backports of both now
([here](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100935)
and
[here](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100964)).
Thanks!
On Monday, 7 June 2021 at 10:38:08 UTC, Max Samukha wrote:
Would be great if you did. Not a blocker, though.
However, this is a major pain:
```d
struct FP {
}
alias parse = () {
FP[] parts;
parts ~= FP();
return parts;
};
immutable s = parse();
extern(C) int main() {
On Sunday, 6 June 2021 at 22:39:34 UTC, Johan Engelen wrote:
it's fun
Hell Yeah! )
On Sunday, 6 June 2021 at 21:18:01 UTC, Iain Buclaw wrote:
That sounds a lot like this issue:
https://issues.dlang.org/show_bug.cgi?id=17857
Most certainly.
Can backport that for GCC-11.
Would be great if you did. Not a blocker, though.
On Sunday, 6 June 2021 at 18:57:06 UTC, Max Samukha wrote:
2) 'align' is mishandled
GCC's bugzilla won't let me register.
align(4)
struct S {
ubyte[4] bytes;
}
static assert (S.alignof == 4); // fail, S.alignof == 1
It's not specific to AVR. Worked around by placing 'align' inside
the
On Friday, 4 June 2021 at 21:47:21 UTC, Iain Buclaw wrote:
You should have better luck using gdc on avr.
https://explore.dgnu.org/z/bos5ee
Trying that, thank you. For now, two issues with GDC 11, which I
hope to work around: 1) compiler complains about typeinfos of
structs used in CTFE
On Friday, 4 June 2021 at 15:48:50 UTC, rikki cattermole wrote:
Does this form of foreach work?
foreach(i; 0 .. 10)
That does work.
This doesn't:
ubyte[] slice;
foreach (ubyte i; slice) {
}
Invalid bitcast
%17 = bitcast i16 %15 to i32
I guess the cause is the same - slice.length.sizeof
On Tuesday, 1 June 2021 at 11:57:34 UTC, Mike Parker wrote:
Dylan Graham writes about his experience using D in a
microcontroller project and why he chose it. Does anyone know
of any similar projects using D? I don't. This may well be the
first time it's been employed in this specific manner.
On Thursday, 4 March 2021 at 13:54:48 UTC, Mike Parker wrote:
The blog:
https://dlang.org/blog/2021/03/04/symphony-of-destruction-structs-classes-and-the-gc-part-one/
"The destructors of all stack-allocated structs in a given scope
are invoked when the scope exits."
Please add a note that
On Monday, 15 June 2020 at 14:55:37 UTC, Andrej Mitrovic wrote:
On Monday, 15 June 2020 at 14:18:38 UTC, Timon Gehr wrote:
Apparently, it has been fixed in 2.092. Nice!
Oh wow that's fantastic. Does anyone know which changeset / PR
fixed it?
The person who fixed that must be commended.
On Monday, 15 June 2020 at 13:57:01 UTC, Max Samukha wrote:
void main() {
Tuple!(byte, int, short) t;
writeln(t[0]);
}
test.d(57,23): Error: need `this` for `__value_field_2` of
type `byte`
It should work. This works:
void main() {
Tuple!(byte, int, short) t;
t[0] = 0;
On Monday, 15 June 2020 at 13:50:07 UTC, Andrej Mitrovic wrote:
typeof(t[0]) works fine, but reading or assigning to such a
field will not work. For example:
void main() {
Tuple!(byte, int, short) t;
writeln(t[0]);
}
test.d(57,23): Error: need `this` for `__value_field_2` of
type
On Sunday, 14 June 2020 at 23:30:03 UTC, Andrei Alexandrescu
wrote:
It's really easy if members in the layout are given internal
names that include information about the original index.
You can construct a list of member aliases in the original order
and then 'alias this' that:
import
23 matches
Mail list logo
