On Monday, 8 July 2024 at 07:29:27 UTC, aberba wrote:
On Sunday, 7 July 2024 at 15:35:36 UTC, Andrey Zherikov wrote:
On Sunday, 7 July 2024 at 14:49:52 UTC, Anonymouse wrote:
On Sunday, 7 July 2024 at 14:41:31 UTC, Andrey Zherikov wrote:
```d
import std.path;
// Error: no property
On Sunday, 7 July 2024 at 15:35:36 UTC, Andrey Zherikov wrote:
On Sunday, 7 July 2024 at 14:49:52 UTC, Anonymouse wrote:
On Sunday, 7 July 2024 at 14:41:31 UTC, Andrey Zherikov wrote:
```d
import std.path;
// Error: no property `asNormaliedPath` for
`dirName("/sandbox/onlineapp.d")` of type
On Sunday, 7 July 2024 at 15:35:36 UTC, Andrey Zherikov wrote:
On Sunday, 7 July 2024 at 14:49:52 UTC, Anonymouse wrote:
On Sunday, 7 July 2024 at 14:41:31 UTC, Andrey Zherikov wrote:
```d
import std.path;
// Error: no property `asNormaliedPath` for
`dirName("/sandbox/onlineapp.d")` of type
On Sunday, 7 July 2024 at 14:49:52 UTC, Anonymouse wrote:
On Sunday, 7 July 2024 at 14:41:31 UTC, Andrey Zherikov wrote:
```d
import std.path;
// Error: no property `asNormaliedPath` for
`dirName("/sandbox/onlineapp.d")` of type `string`
auto p = __FILE_FULL_PATH__.dirName.asNormaliedPath;
On Sun, Jul 07, 2024 at 02:41:31PM +, Andrey Zherikov via
Digitalmars-d-learn wrote:
> Seems different functions in std.path do not work together:
> ```d
> import std.path;
>
> // Error: no property `asNormaliedPath` for
> `dirName("/sandbox/onlineapp.d")` of type `string`
> auto p =
On Sunday, 7 July 2024 at 14:41:31 UTC, Andrey Zherikov wrote:
```d
import std.path;
// Error: no property `asNormaliedPath` for
`dirName("/sandbox/onlineapp.d")` of type `string`
auto p = __FILE_FULL_PATH__.dirName.asNormaliedPath;
```
`asNormalizedPath` is misspelled.
On 1/11/23 18:26, Christian Köstlin wrote:
It's really weird: https://run.dlang.io/is/fIBR2n
I think I might have found out the issue. It's indeed related to the
lazy parameter and reentrance.
The usual logger functions consist of three parts: a header, the
message, and the "finalizer
On Wednesday, 1 November 2023 at 17:26:42 UTC, Christian Köstlin
wrote:
...
It's really weird: https://run.dlang.io/is/fIBR2n
Interesting because I wrote a similar test as you did. And that
increment (Or lack of) called my attention, If I can I'll try and
take a look at that (std.logger
n foo");
return "Hello, world.";
}
```
...
Unless you do:
string s;
info(s=foo());
I think this is a bug, or at least very weird behavior.
Matheus.
It's really weird: https://run.dlang.io/is/fIBR2n
On Wednesday, 1 November 2023 at 16:24:04 UTC, BoQsc wrote:
**Error:**
```
rdmd testimport.d
testimport.d(2): Error: module `next` from file waffle\next.d
must be imported with 'import next;'
```
You import 'waffle.next', but the module is inferred to be
'next'. If put `module
I'm unable to import a `.d` source file from a subfolder.
Now this happens only with `rdmd`.
The `dmd -i -run` works perfectly.
I'm currently on Windows 10 operating system.
**./testimport.d**:
```
import std;
import waffle.next;
void main(){
writeln("test", testing);
}
```
...
Unless you do:
string s;
info(s=foo());
I think this is a bug, or at least very weird behavior.
Matheus.
I can only imagine that it's related to the logging functions taking
lazy arguments, although I cannot see why it would be a problem in a
simple case like this.
I've been thinking a bit more about it, and it must be indeed because of
the lazy argument.
`foo()` is an argument to `info`, but
Hi,
Today I have just found a weird bug in std.logger. Consider:
```d
import std.logger : info;
void main() {
info(foo());
}
auto foo() {
info("In foo");
return "Hello, world.";
}
```
The output is:
```
2023-10-31T20:41:05.274 [info] onlineapp.d:8:foo In
On Wednesday, 20 September 2023 at 13:53:08 UTC, Ki Rill wrote:
Here is the macro:
```C
#define NK_CONTAINER_OF(ptr,type,member)\
(type*)((void*)((char*)(1 ? (ptr): &((type*)0)->member) -
NK_OFFSETOF(type, member)))
```
I'm trying to translate the Nuklear GUI library to D
On Thursday, 21 September 2023 at 16:50:51 UTC, Imperatorn wrote:
On Wednesday, 20 September 2023 at 13:53:08 UTC, Ki Rill wrote:
Here is the macro:
```C
#define NK_CONTAINER_OF(ptr,type,member)\
(type*)((void*)((char*)(1 ? (ptr): &((type*)0)->member) -
NK_OFFSETOF(type, member)))
```
On Thursday, 21 September 2023 at 16:28:25 UTC, Nick Treleaven
wrote:
The 1st argument of `getMember` can just be T, like the
original macro.
The 2nd argument needs to be a compile-time string.
Also the `char*` cast needs to apply to `ptr` before
subtracting the offset AFAICS.
So
On Wednesday, 20 September 2023 at 13:53:08 UTC, Ki Rill wrote:
Here is the macro:
```C
#define NK_CONTAINER_OF(ptr,type,member)\
(type*)((void*)((char*)(1 ? (ptr): &((type*)0)->member) -
NK_OFFSETOF(type, member)))
```
I'm trying to translate the Nuklear GUI library to D
On Thursday, 21 September 2023 at 16:28:25 UTC, Nick Treleaven
wrote:
(Untested)
There might be a `need this` error
On Thursday, 21 September 2023 at 16:28:25 UTC, Nick Treleaven
wrote:
return cast(T*)(cast(void*)(cast(char*)ptr -
__traits(getMember, T, member).offsetof)));
There's a trailing `)` that needs removing. Also pretty sure it
can be simplified to:
return cast(T*)(cast(char*)ptr
On Thursday, 21 September 2023 at 02:57:07 UTC, Ki Rill wrote:
On Thursday, 21 September 2023 at 02:23:32 UTC, Ki Rill wrote:
wrote:
[...]
Translated it to this eventually:
```D
auto nk_container_of(P, T)(P ptr, T type, const(char)* member)
{
return cast(T*)(cast(void*)(cast(char*)
On Thursday, 21 September 2023 at 02:23:32 UTC, Ki Rill wrote:
wrote:
[...]
Translated it to this eventually:
```D
auto nk_container_of(P, T)(P ptr, T type, const(char)* member)
{
return cast(T*)(cast(void*)(cast(char*)
(ptr - __traits(getMember, type, member).offsetof)));
}
```
On Wednesday, 20 September 2023 at 17:14:41 UTC, Dejan Lekic
wrote:
[...]
NK_CONTAINER_OF should probably be translated to:
`cast(T*)((cast(void*)ptr - __traits(getMember, T,
member).offsetof))`
PS. I did not invent this. My original idea was far worse than
this. - It was suggested on IRC
On Wednesday, 20 September 2023 at 13:55:14 UTC, Ki Rill wrote:
On Wednesday, 20 September 2023 at 13:53:08 UTC, Ki Rill wrote:
Here is the macro:
```C
#define NK_CONTAINER_OF(ptr,type,member)\
(type*)((void*)((char*)(1 ? (ptr): &((type*)0)->member) -
NK_OFFSETOF(type, member)))
```
I'm
](https://github.com/rillki/nuklear-d/tree/nuklear-d-translation).
My workflow when trying to port weird C code to D is to have a
small C file, put an example code, and then run the preprocessor,
and try to get how things are expanded
Alternatively, latest version of visual studio allows you
On Wednesday, 20 September 2023 at 13:55:14 UTC, Ki Rill wrote:
On Wednesday, 20 September 2023 at 13:53:08 UTC, Ki Rill wrote:
Here is the macro:
```C
#define NK_CONTAINER_OF(ptr,type,member)\
(type*)((void*)((char*)(1 ? (ptr): &((type*)0)->member) -
NK_OFFSETOF(type, member)))
```
I'm
On Wednesday, 20 September 2023 at 13:53:08 UTC, Ki Rill wrote:
Here is the macro:
```C
#define NK_CONTAINER_OF(ptr,type,member)\
(type*)((void*)((char*)(1 ? (ptr): &((type*)0)->member) -
NK_OFFSETOF(type, member)))
```
I'm trying to translate the Nuklear GUI library to D
Here is the macro:
```C
#define NK_CONTAINER_OF(ptr,type,member)\
(type*)((void*)((char*)(1 ? (ptr): &((type*)0)->member) -
NK_OFFSETOF(type, member)))
```
I'm trying to translate the Nuklear GUI library to D
[here](https://github.com/rillki/nuklear-d/tree/nuklear-d-translation).
On Thursday, 14 September 2023 at 03:23:48 UTC, An Pham wrote:
import std.stdio;
void main()
{
float f = 6394763.345f;
import std.format : sformat;
char[80] vBuffer = void;
writeln("6394763.345 = ", sformat(vBuffer[], "%.4f",
f));
On Wednesday, September 13, 2023 9:23:48 PM MDT An Pham via Digitalmars-d-
learn wrote:
> import std.stdio;
>
> void main()
> {
> float f = 6394763.345f;
>
> import std.format : sformat;
>
> char[80] vBuffer = void;
> writeln("6394763.345 = ",
import std.stdio;
void main()
{
float f = 6394763.345f;
import std.format : sformat;
char[80] vBuffer = void;
writeln("6394763.345 = ", sformat(vBuffer[], "%.4f", f));
}
Output
6394763.345 = 6394763.5000
On Sunday, 9 July 2023 at 14:49:39 UTC, Steven Schveighoffer
wrote:
This is probably a bug somewhere, 4 seconds is too much. A
reduced test case would be helpful.
But I wanted to note, inside a struct template, the template
name (by itself) is equivalent to the current instantiation. So
On 7/9/23 7:54 AM, IchorDev wrote:
While working on some new bindings, I've discovered that if `opAssign`
in a struct template "`BindingTempl(T)`" has the return type
"`BindingTempl!T` then it adds about 4 seconds to the compile time per
instantiation of `BindingTempl`. The added compile time
While working on some new bindings, I've discovered that if
`opAssign` in a struct template "`BindingTempl(T)`" has the
return type "`BindingTempl!T` then it adds about 4 seconds to the
compile time per instantiation of `BindingTempl`. The added
compile time is much lower if a function other
https://issues.dlang.org/show_bug.cgi?id=23950
RazvanN changed:
What|Removed |Added
Keywords||backend, ice
CC|
https://issues.dlang.org/show_bug.cgi?id=23950
--- Comment #1 from m...@ernestocastellotti.it ---
The absurd thing is that instead this code compiles and works correctly:
import core.stdc.stdlib;
void main() {
auto foo = (false != true) && true || abort();
}
This looks just like a bad bug
https://issues.dlang.org/show_bug.cgi?id=23950
Issue ID: 23950
Summary: Weird backend fail with noreturn type - cod1.d(4027):
Assertion failure
Product: D
Version: D2
Hardware: x86_64
OS: Linux
On Thursday, 7 April 2022 at 12:51:26 UTC, Stanislav Blinov wrote:
On Thursday, 7 April 2022 at 10:50:35 UTC, BoQsc wrote:
wchar_t* clang_string = cast(wchar_t *)"AA";
You're witnessing undefined behavior. "AA" is a string
literal and is stored in the data
On Thursday, 7 April 2022 at 10:50:35 UTC, BoQsc wrote:
wchar_t* clang_string = cast(wchar_t *)"AA";
You're witnessing undefined behavior. "AA" is a string
literal and is stored in the data segment. Mere cast to wchar_t*
does not make writing through that
On Thursday, 7 April 2022 at 11:03:39 UTC, Tejas wrote:
On Thursday, 7 April 2022 at 10:50:35 UTC, BoQsc wrote:
Here I try to concatenate three character strings using
`wcsncat()`.
[...]
Maybe try using `wstring` instead of string? Also use the `w`
postfix
```d
wstring dlang_string =
On Thursday, 7 April 2022 at 10:50:35 UTC, BoQsc wrote:
Here I try to concatenate three character strings using
`wcsncat()`.
[...]
Maybe try using `wstring` instead of string? Also use the `w`
postfix
```d
wstring dlang_string = "BBB"w;
I can't test because I'm not on my PC and I
Here I try to concatenate three character strings using
`wcsncat()`.
`clang_string` AA
`dlang_string` BBB
`winpointer_to_string` CC
```
import std.stdio;
@system void main(){
import std.utf: toUTF16z, toUTF16;
import
On 7/23/21 3:30 PM, apz28 wrote:
On Friday, 23 July 2021 at 18:44:47 UTC, Steven Schveighoffer wrote:
On 7/22/21 7:43 PM, apz28 wrote:
In any case, it's possible that fbConnection being null does not mean
a null dereference, but I'd have to see the class itself. I'm
surprised if you don't
On 7/23/21 12:30 PM, apz28 wrote:
> The -debug build with passing unit-tests so no problem there.
> The -release build is having problem. After make change to accommodate
> it, it takes forever to build. I started it yesterday 11AM and it is
> still compiling now (more than a day already.) It
On Friday, 23 July 2021 at 18:44:47 UTC, Steven Schveighoffer
wrote:
On 7/22/21 7:43 PM, apz28 wrote:
In any case, it's possible that fbConnection being null does
not mean a null dereference, but I'd have to see the class
itself. I'm surprised if you don't get a null dereference in
On 7/22/21 7:43 PM, apz28 wrote:
FbConnection is a class, FbXdrReader is a struct and for this call,
response.data is not null & its' length will be greater than zero and
FbConnection is not being used. So why DMD try to evaluate at compiled
time hence error
1. Should not evaluate at compile
On Thursday, 22 July 2021 at 18:56:43 UTC, Steven Schveighoffer
wrote:
On 7/22/21 2:38 PM, apz28 wrote:
On Wednesday, 21 July 2021 at 20:39:54 UTC, Dukc wrote:
On Wednesday, 21 July 2021 at 14:15:51 UTC, Steven
Schveighoffer wrote:
2. It's hard for me to see where the null dereference would
On 7/22/21 2:38 PM, apz28 wrote:
On Wednesday, 21 July 2021 at 20:39:54 UTC, Dukc wrote:
On Wednesday, 21 July 2021 at 14:15:51 UTC, Steven Schveighoffer wrote:
2. It's hard for me to see where the null dereference would be in
that function (the `bool` implementation is pretty simple).
DMD
On Wednesday, 21 July 2021 at 20:39:54 UTC, Dukc wrote:
On Wednesday, 21 July 2021 at 14:15:51 UTC, Steven
Schveighoffer wrote:
2. It's hard for me to see where the null dereference would be
in that function (the `bool` implementation is pretty simple).
-Steve
DMD complains about
On Wednesday, 21 July 2021 at 14:15:51 UTC, Steven Schveighoffer
wrote:
2. It's hard for me to see where the null dereference would be
in that function (the `bool` implementation is pretty simple).
-Steve
DMD complains about dereferences in three different lines. I
suspect it's `this`
On 7/21/21 7:56 AM, apz28 wrote:
On Wednesday, 21 July 2021 at 11:52:39 UTC, apz28 wrote:
On Wednesday, 21 July 2021 at 04:52:44 UTC, Mathias LANG wrote:
It seems the compiler is doing extra analysis and seeing that a null
pointer is being dereferenced. Can you provide the code for
On Wednesday, 21 July 2021 at 03:25:03 UTC, apz28 wrote:
VisualD project - Any hint to work around
DMD version:
DMD32 D Compiler v2.096.0-rc.1-dirty
Copyright (C) 1999-2021 by The D Language Foundation, All
Rights Reserved written by Walter Bright
Failed Build Command line:
dmd -release
On Wednesday, 21 July 2021 at 11:52:39 UTC, apz28 wrote:
On Wednesday, 21 July 2021 at 04:52:44 UTC, Mathias LANG wrote:
It seems the compiler is doing extra analysis and seeing that
a null pointer is being dereferenced. Can you provide the code
for "pham\db\db_skdatabase.d" at L138 through
On Wednesday, 21 July 2021 at 04:52:44 UTC, Mathias LANG wrote:
It seems the compiler is doing extra analysis and seeing that a
null pointer is being dereferenced. Can you provide the code
for "pham\db\db_skdatabase.d" at L138 through 140 ?
```d
package(pham.db): // Line# 133
On Wednesday, 21 July 2021 at 03:25:03 UTC, apz28 wrote:
with below error message:
..\..\pham\db\db_skdatabase.d(140): Error: null dereference in
function
_D4pham2db10fbdatabase7FbArray__T13readArrayImplTbZQsMFNfCQCeQCc8database12DbNameColumnZAb
..\..\pham\db\db_skdatabase.d(139): Error: null
VisualD project - Any hint to work around
DMD version:
DMD32 D Compiler v2.096.0-rc.1-dirty
Copyright (C) 1999-2021 by The D Language Foundation, All Rights
Reserved written by Walter Bright
Failed Build Command line:
dmd -release -m32mscoff -O -inline -dip25 -dip1000
-preview=fixAliasThis
On Wednesday, 28 April 2021 at 06:06:47 UTC, Rainer Schuetze
wrote:
On 26/04/2021 20:22, Imperatorn wrote:
On Monday, 26 April 2021 at 17:37:26 UTC, Rainer Schuetze
wrote:
On 26/04/2021 10:00, Raimondo Mancino wrote:
[...]
The problem is that the semantic engine used by Visual D is
On 26/04/2021 20:22, Imperatorn wrote:
> On Monday, 26 April 2021 at 17:37:26 UTC, Rainer Schuetze wrote:
>>
>> On 26/04/2021 10:00, Raimondo Mancino wrote:
>>> [...]
>>
>> The problem is that the semantic engine used by Visual D is working
>> with the DMD frontend of 2.095, but "noreturn" is a
On Monday, 26 April 2021 at 17:37:26 UTC, Rainer Schuetze wrote:
On 26/04/2021 10:00, Raimondo Mancino wrote:
[...]
The problem is that the semantic engine used by Visual D is
working with the DMD frontend of 2.095, but "noreturn" is a new
language feature introduced with 2.096.
You can
hese.
>
> I was trying the Visual D extension to Visual Studio, but after the
> first code generation (DLL library, x86 & x64 both checked), I get this
> weird error:
>
> ```
> C:\D\dmd2\src\druntime\import\core\sys\windows\dll.d:
> \object.d(18): can only `*` a pointer,
On Monday, 26 April 2021 at 15:54:36 UTC, Adam D. Ruppe wrote:
Do you have a separate object.d in your current directory? That
can cause all kinds of weird errors.
Otherwise I suspect this is a conflict between two versions of
the compiler. If you had one installed before then updated
On Monday, 26 April 2021 at 08:00:08 UTC, Raimondo Mancino wrote:
C:\D\dmd2\src\druntime\import\core\sys\windows\dll.d:
\object.d(18): can only `*` a pointer, not a `typeof(null)`
Do you have a separate object.d in your current directory? That
can cause all kinds of weird errors.
Otherwise
On Monday, 26 April 2021 at 14:17:34 UTC, Imperatorn wrote:
Also, be sure to join on Discord as well
(https://discord.gg/bMZk9Q4) if you're not already there!
Thank you, I think I'll join.
On Monday, 26 April 2021 at 10:42:54 UTC, Mike Parker wrote:
(According to -v: DMD64 D Compiler v2.096.0-dirty)
That's actually normal for the Windows versions. I'm not sure
where it comes from, but it's always there.
Ouuu, that's bad advertising, isn't it? Who wants to use dirty
software, it
On Monday, 26 April 2021 at 11:03:19 UTC, Raimondo Mancino wrote:
On Monday, 26 April 2021 at 10:44:14 UTC, Mike Parker wrote:
You might try to build outside of VS and see if you get the
same errors.
The weird thing is that I get these errors just in the errors
frame, but building works just
On Monday, 26 April 2021 at 11:03:19 UTC, Raimondo Mancino wrote:
On Monday, 26 April 2021 at 10:44:14 UTC, Mike Parker wrote:
You might try to build outside of VS and see if you get the
same errors.
The weird thing is that I get these errors just in the errors
frame, but building works just
On Monday, 26 April 2021 at 10:44:14 UTC, Mike Parker wrote:
You might try to build outside of VS and see if you get the
same errors.
The weird thing is that I get these errors just in the errors
frame, but building works just fine without errors.
If I run devenv.exe directly
On Monday, 26 April 2021 at 10:40:44 UTC, Johann Lermer wrote:
On Monday, 26 April 2021 at 08:58:25 UTC, Raimondo Mancino
wrote:
According to -v: DMD64 D Compiler v2.096.0-dirty
Well, that says it all, doesn't it? I'm not familiar with the
windows versions, but that doesn't seem to be an
On Monday, 26 April 2021 at 08:00:08 UTC, Raimondo Mancino wrote:
Since these are thrown by the standard library, I suspect this
could be a bug; but maybe I'm just missing something?
Thank you for your help.
You might try to build outside of VS and see if you get the same
errors.
On Monday, 26 April 2021 at 08:58:25 UTC, Raimondo Mancino wrote:
According to -v: DMD64 D Compiler v2.096.0-dirty
Well, that says it all, doesn't it? I'm not familiar with the
windows versions, but that doesn't seem to be an offical release
- at least I never had a dmd2 that claimed to be
On Monday, 26 April 2021 at 08:40:01 UTC, Imperatorn wrote:
On Monday, 26 April 2021 at 08:00:08 UTC, Raimondo Mancino
wrote:
Hello, I'm new to the language; I just started learning it a
few months ago. I'm doing okay with it, I find it very
versatile and fast to learn. I come from Java and
On Monday, 26 April 2021 at 08:00:08 UTC, Raimondo Mancino wrote:
Hello, I'm new to the language; I just started learning it a
few months ago. I'm doing okay with it, I find it very
versatile and fast to learn. I come from Java and C/C++ and I
think D solves tons of problems I had with these.
the first code generation (DLL library, x86 & x64 both checked),
I get this weird error:
```
C:\D\dmd2\src\druntime\import\core\sys\windows\dll.d:
\object.d(18): can only `*` a pointer, not a `typeof(null)`
```
So I opened the object.d in VS and apparently, this is the line
of code it's yel
On 4/9/21 11:17 AM, Berni44 wrote:
> I'm on reworking completely the docs of `std.format`.
Awesome! :)
Ali
On Friday, 9 April 2021 at 16:11:26 UTC, Oleg B wrote:
valid '1/1/1': 0001-Jan-01 00:00:00 <<< see here
[...]
Is space a special char for `formattedRead` and it simple stop
parse without throwing exception if not found space (that
represented in fmt string)?
Have `formattedRead` any other
On Friday, 9 April 2021 at 16:11:26 UTC, Oleg B wrote:
Is space a special char for `formattedRead` and it simple stop
parse without throwing exception if not found space (that
represented in fmt string)?
Have `formattedRead` any other special chars?
Or it's bug?
I think it's a bug:
The
On 4/9/21 9:11 AM, Oleg B wrote:
> Is space a special char for `formattedRead` and it simple stop parse
> without throwing exception if not found space
Yes: The space character means "zero or more white space".
Ali
P.S. I can't check whether the D standard library documentation includes
that
Hello, I have some doubts about working `formattedRead` with
space chars.
Example:
```d
import std : formattedRead, DateTime, stderr, each;
DateTime parseDT(string str)
{
int d,mo,y, h,m,s;
formattedRead!"%d/%d/%d %d:%d:%d"(str, d,mo,y, h,m,s);
return DateTime(y,mo,d, h,m,s);
}
On Thursday, 28 January 2021 at 13:13:46 UTC, Paul Backus wrote:
...
https://issues.dlang.org/show_bug.cgi?id=21589
These issues are always so subtle and specific yet so annoying,
e.g.:
https://issues.dlang.org/show_bug.cgi?id=21496
and
https://issues.dlang.org/show_bug.cgi?id=21377
On Thursday, 28 January 2021 at 13:07:13 UTC, SealabJaster wrote:
Please see: https://run.dlang.io/is/2mwcPH
I'd expect that the `isInstanceOf` would be true instead of
false here.
Commenting out the public import changes the output of
`fullyQualifiedName`. I can kind of see why this
Please see: https://run.dlang.io/is/2mwcPH
I'd expect that the `isInstanceOf` would be true instead of false
here.
Commenting out the public import changes the output of
`fullyQualifiedName`. I can kind of see why this happens, but
it's kind of annoying when things like `isInstanceOf`
https://issues.dlang.org/show_bug.cgi?id=17436
--- Comment #3 from kinke ---
Ah sorry, that's for signed long only.
--
https://issues.dlang.org/show_bug.cgi?id=17436
--- Comment #2 from kinke ---
[The generated code uses the ucomisd instruction, which is SSE2, so using
cvtsi2sd (SSE2) and avoiding the x87 should be feasible.]
--
https://issues.dlang.org/show_bug.cgi?id=17436
Walter Bright changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.dlang.org/show_bug.cgi?id=17436
Walter Bright changed:
What|Removed |Added
Keywords||backend
CC|
https://issues.dlang.org/show_bug.cgi?id=21123
kinke changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.dlang.org/show_bug.cgi?id=21123
--- Comment #3 from kinke ---
(In reply to kinke from comment #2)
> Seems to be fixed indeed according to run.dlang.io.
Well I've assumed the nightly build there was up-to-date, but it's some old
v2.091 build (as is the Windows nightly download). -
https://issues.dlang.org/show_bug.cgi?id=21123
--- Comment #2 from kinke ---
Seems to be fixed indeed according to run.dlang.io. I'd like to see this in the
v2.093.1 point release though, as it would e.g. seriously impede LDC debugging
(-vv output etc.) for upcoming v1.23.
--
https://issues.dlang.org/show_bug.cgi?id=21123
RazvanN changed:
What|Removed |Added
CC||razvan.nitu1...@gmail.com
--- Comment #1 from
https://issues.dlang.org/show_bug.cgi?id=21123
Walter Bright changed:
What|Removed |Added
Keywords||ice-on-valid-code
CC|
https://issues.dlang.org/show_bug.cgi?id=21123
Issue ID: 21123
Summary: ICE during toChars() of weird CommaExp lowering
Product: D
Version: D2
Hardware: All
OS: All
Status: NEW
Severity: regression
https://issues.dlang.org/show_bug.cgi?id=18831
Paul Backus changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
On Saturday, 13 June 2020 at 13:08:29 UTC, realhet wrote:
How can be a string represented with 'null' by default instead
on `""`. Unless I state it explicitly with name="" ? o.O
Because string is simply `alias string = immutable(char)[]`, and
default initializer for arrays is null.
On Saturday, 13 June 2020 at 12:55:36 UTC, realhet wrote:
Hello, I have a problem I can't even understand with the code
For the first I realized that an UDA can be a type too, and come
up with this:
template getUDA(alias a, U){
enum u = q{ getUDAs!(a, U)[$-1] };
static if(hasUDA!(a,
On Saturday, 13 June 2020 at 12:55:36 UTC, realhet wrote:
My first question is, how to avoid that error with A.i4? Why
is there a difference between @UNIFORM and @UNIFORM(), do the
first returns a type and the later returns a value?
Basically yeah. a UDA in D is just whatever you write gets
Hello, I have a problem I can't even understand with the code
below:
https://run.dlang.io/is/7yXAEA
import std.stdio, std.range, std.algorithm, std.traits, std.meta;
struct UNIFORM{ string name; }
struct A{
int i1;
@UNIFORM() int i2;
@UNIFORM("fuzz") int i3;
@UNIFORM int i4;
https://issues.dlang.org/show_bug.cgi?id=10110
Mathias LANG changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://issues.dlang.org/show_bug.cgi?id=6318
Basile-z changed:
What|Removed |Added
CC|b2.t...@gmx.com |
--
https://issues.dlang.org/show_bug.cgi?id=18303
Basile-z changed:
What|Removed |Added
CC|b2.t...@gmx.com |
--
https://issues.dlang.org/show_bug.cgi?id=15028
berni44 changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
1 - 100 of 631 matches
Mail list logo
