On 4/27/23 2:17 PM, Sergey wrote:
On Thursday, 27 April 2023 at 17:42:30 UTC, Steven Schveighoffer wrote:
On 4/16/23 11:39 AM, Steven Schveighoffer wrote:
# BEERCONF!
Beerconf for April is happening 2 weeks from now, on the 29-30.
A reminder that this is happening in 2 days!
##
On Thursday, 27 April 2023 at 17:42:30 UTC, Steven Schveighoffer
wrote:
On 4/16/23 11:39 AM, Steven Schveighoffer wrote:
# BEERCONF!
Beerconf for April is happening 2 weeks from now, on the 29-30.
A reminder that this is happening in 2 days!
## Presentations?
This beerconf, we have
On 4/16/23 11:39 AM, Steven Schveighoffer wrote:
# BEERCONF!
Beerconf for April is happening 2 weeks from now, on the 29-30.
A reminder that this is happening in 2 days!
## Presentations?
This beerconf, we have another presentation! Hipreme will show off the
HipremeEngine build system:
On Thursday, 27 April 2023 at 06:10:57 UTC, Basile B. wrote:
It's a misconception of the problem that the DIP tried to
solve. What the DIP tried to solve is that the compiler should
know that you are using an enum member. Actually I even think
this should work without any special syntax, as a
On Thursday, 27 April 2023 at 06:10:57 UTC, Basile B. wrote:
On Thursday, 27 April 2023 at 00:16:10 UTC, Walter Bright wrote:
This also works:
alias F = MySuperLongNameFlag;
auto flag = F.A | F.B | F.C | F.D;
set_flags(F.A | F.B | F.C | F.D);
It's similar to setting a local
On Thursday, 27 April 2023 at 00:16:10 UTC, Walter Bright wrote:
This also works:
alias F = MySuperLongNameFlag;
auto flag = F.A | F.B | F.C | F.D;
set_flags(F.A | F.B | F.C | F.D);
It's similar to setting a local variable to some complex
expression, just so you don't have to
