| Thread overview | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
August 20, 2021 mir.complex | ||||
|---|---|---|---|---|
| ||||
 | mir.complex [1] has been added to mir-core v1.1.80 Builtin complex numbers have been replaced with mir.complex in the following packages:
[1] http://mir-core.libmir.org/mir_complex.html MRs are welcome. Kind regards, | |||
August 20, 2021 Re: mir.complex | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to 9il | On Friday, 20 August 2021 at 16:44:53 UTC, 9il wrote: >Builtin complex numbers have been replaced with mir.complex in the following packages: Out of curiosity, how did std.complex fall short? | |||
August 20, 2021 Re: mir.complex | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Dennis | On 8/20/21 9:54 AM, Dennis wrote:
> On Friday, 20 August 2021 at 16:44:53 UTC, 9il wrote:
>> Builtin complex numbers have been replaced with mir.complex in the following packages:
>
> Out of curiosity, how did std.complex fall short?
Maybe it was too complex?
Sorry, I'll see myself out.
| |||
August 20, 2021 Re: mir.complex | ||||
|---|---|---|---|---|
| ||||
Posted in reply to Dennis | On Friday, 20 August 2021 at 16:54:07 UTC, Dennis wrote: >On Friday, 20 August 2021 at 16:44:53 UTC, 9il wrote: >Builtin complex numbers have been replaced with mir.complex in the following packages: Out of curiosity, how did std.complex fall short? There are few reasons. The main one is that linking bugs caused by a compiler mangling/generation bugs makes std.complex unusable for us. Initially I have updated all packages with std.complex, however it failed to link in a private project. | |||
August 20, 2021 Re: mir.complex | ||||
|---|---|---|---|---|
| ||||
Posted in reply to David Gileadi | On Friday, 20 August 2021 at 16:55:57 UTC, David Gileadi wrote:
> On 8/20/21 9:54 AM, Dennis wrote:
>> On Friday, 20 August 2021 at 16:44:53 UTC, 9il wrote:
>>> Builtin complex numbers have been replaced with mir.complex in the following packages:
>>
>> Out of curiosity, how did std.complex fall short?
>
> Maybe it was too complex?
>
> Sorry, I'll see myself out.
Yes, it was hard to make std.complex works.
| |||
August 20, 2021 Re: mir.complex | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to 9il | On Friday, 20 August 2021 at 17:03:52 UTC, 9il wrote: >On Friday, 20 August 2021 at 16:55:57 UTC, David Gileadi wrote: >On 8/20/21 9:54 AM, Dennis wrote: >On Friday, 20 August 2021 at 16:44:53 UTC, 9il wrote: >Builtin complex numbers have been replaced with mir.complex in the following packages: Out of curiosity, how did std.complex fall short? Maybe it was too complex? Sorry, I'll see myself out. Yes, it was hard to make std.complex works. This is starting to get too real for me runs away | |||
August 30, 2021 Re: mir.complex | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to 9il | On Friday, 20 August 2021 at 17:02:33 UTC, 9il wrote: >There are few reasons. The main one is that linking bugs caused by a compiler mangling/generation bugs makes std.complex unusable for us. Initially I have updated all packages with std.complex, however it failed to link in a private project. Why wasn't fixing the linking bugs considered an alternative to forking std.complex? What are the other remaining reasons for not using std.complex? | |||
August 30, 2021 Re: mir.complex | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Per Nordlöw | On Monday, 30 August 2021 at 13:26:09 UTC, Per Nordlöw wrote: >[snip] Why wasn't fixing the linking bugs considered an alternative to forking std.complex? What are the other remaining reasons for not using std.complex? It doesn't look like any bug reports were filed. Hopefully that can happen... | |||
Permalink
Reply
