https://issues.dlang.org/show_bug.cgi?id=16692
--- Comment #10 from Manu ---
Okay, that's awesome!
Seems to work well.
So for const pure properties (or methods that look like properties) where it's
safe to call them without mutating, is it possible to automatically populate
the struct/class
https://issues.dlang.org/show_bug.cgi?id=18639
Manu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.dlang.org/show_bug.cgi?id=18846
Manu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Wednesday, 6 June 2018 at 01:34:13 UTC, Arun Chandrasekaran
wrote:
I'm more interested in no/minimal runtime[1] than -betterC for
my use cases.
I think it will be good to have the document mention if the
function is supported without the druntime and/or with
-betterC. This documentation
On Tuesday, 5 June 2018 at 13:54:25 UTC, Steven Schveighoffer
wrote:
On 6/5/18 3:25 AM, Brian wrote:
source code in github https://github.com/huntlabs/hunt/
documents in wiki https://github.com/huntlabs/hunt/wiki/
hunt framework website http://www.huntframework.com/
Is there a way to view
I'm more interested in no/minimal runtime[1] than -betterC for my
use cases.
I think it will be good to have the document mention if the
function is supported without the druntime and/or with -betterC.
This documentation can be the module level or function level. Is
this possible and/or is
https://issues.dlang.org/show_bug.cgi?id=18949
Issue ID: 18949
Summary: Array literals don't work with betterc
Product: D
Version: D2
Hardware: x86
OS: Windows
Status: NEW
Severity: enhancement
On 05.06.2018 21:05, DigitalDesigns wrote:
On Tuesday, 5 June 2018 at 18:46:41 UTC, Timon Gehr wrote:
On 05.06.2018 18:50, DigitalDesigns wrote:
With a for loop, it is pretty much a wrapper on internal cpu logic so
it will be near as fast as possible.
This is not even close to being true for
On Tuesday, 5 June 2018 at 17:12:00 UTC, Apocalypto wrote:
On Tuesday, 5 June 2018 at 16:12:25 UTC, RalphBa wrote:
Did you ever have the need to write something efficient? .NET
is a sandbox for children and UX people.
Oh yeah, toy applications for children like StackOverflow,
Siemens NX,
On Tuesday, 5 June 2018 at 21:53:51 UTC, I love Ice Cream wrote:
On Tuesday, 5 June 2018 at 20:15:07 UTC, Jonathan M Davis wrote:
On Tuesday, June 05, 2018 15:09:56 Dejan Lekic via
Digitalmars-d wrote:
On Sunday, 3 June 2018 at 17:40:46 UTC, I love Ice Cream
wrote:
>> Is D really a top 20
On Tuesday, 5 June 2018 at 22:28:44 UTC, DigitalDesigns wrote:
On Tuesday, 5 June 2018 at 21:35:03 UTC, Steven Schveighoffer
wrote:
[...]
[...]
Does ranges not evaluate lazily on some cases. So it'll avoid
unnecessary work...and be much faster and efficient. If I'm
correct.
[...]
On Tuesday, 5 June 2018 at 21:35:03 UTC, Steven Schveighoffer
wrote:
On 6/5/18 5:22 PM, DigitalDesigns wrote:
On Tuesday, 5 June 2018 at 20:07:06 UTC, Ethan wrote:
In conclusion. The semantics you talk about are literally
some of the most basic instructions in computing; and that
escaping
On Tuesday, 5 June 2018 at 22:20:08 UTC, DigitalDesigns wrote:
It doesn't matter! The issue that I said was not that ranges
were slower but that ranges exist on an abstract on top of
language semantics! that means that they can never be faster
than the language itself! Anything that a range
On Tuesday, 5 June 2018 at 19:18:15 UTC, Adam D. Ruppe wrote:
On Tuesday, 5 June 2018 at 19:05:27 UTC, DigitalDesigns wrote:
For loops HAVE a direct cpu semantic! Do you doubt this?
What are they?
And for bonus points, are they actually used by compilers?
Then the final question: is the
On Tuesday, June 05, 2018 22:08:32 Stefan Koch via Digitalmars-d-learn
wrote:
> On Tuesday, 5 June 2018 at 18:00:05 UTC, Steven Schveighoffer
>
> wrote:
> > No, it's definitely a bug. main is not being evaluated at
> > compile time. The real result of this function should be a
> > compile-time
On Tuesday, 5 June 2018 at 18:00:05 UTC, Steven Schveighoffer
wrote:
No, it's definitely a bug. main is not being evaluated at
compile time. The real result of this function should be a
compile-time error -- __ctfe is a *runtime* value that is
always defined based on whether you are __ctfe
On Tuesday, 5 June 2018 at 21:54:20 UTC, DigitalDesigns wrote:
You are an idiot!
Take it to reddit. Back your arguments up with actual knowledge
and intelligence, not unfounded agression.
On Tuesday, 5 June 2018 at 21:52:03 UTC, Ethan wrote:
On Tuesday, 5 June 2018 at 21:22:27 UTC, DigitalDesigns wrote:
Ok asshat!
Take it to reddit. Back your arguments up with actual knowledge
and intelligence, not unfounded agression.
You are an idiot! You obviously do not understand basic
On Tuesday, 5 June 2018 at 21:22:27 UTC, DigitalDesigns wrote:
Ok asshat!
Take it to reddit. Back your arguments up with actual knowledge
and intelligence, not unfounded agression.
On Tuesday, 5 June 2018 at 20:15:07 UTC, Jonathan M Davis wrote:
On Tuesday, June 05, 2018 15:09:56 Dejan Lekic via
Digitalmars-d wrote:
On Sunday, 3 June 2018 at 17:40:46 UTC, I love Ice Cream wrote:
>> Is D really a top 20 language? I don't remember seeing it
>> anywhere close to the top 20.
On 6/5/18 5:22 PM, DigitalDesigns wrote:
On Tuesday, 5 June 2018 at 20:07:06 UTC, Ethan wrote:
In conclusion. The semantics you talk about are literally some of the
most basic instructions in computing; and that escaping the confines
of a for loop for a foreach loop can let the compiler
On Tuesday, 5 June 2018 at 20:07:06 UTC, Ethan wrote:
On Tuesday, 5 June 2018 at 19:05:27 UTC, DigitalDesigns wrote:
For loops HAVE a direct cpu semantic! Do you doubt this?
...
Right. If you're gonna keep running your mouth off. How about
looking at some disassembly then.
for(auto i=0;
On 6/5/18 5:03 PM, FeepingCreature wrote:
On Tuesday, 5 June 2018 at 17:47:15 UTC, Steven Schveighoffer wrote:
Another observation: under the "infinite loops are important
observable behavior" world-view, pure functions cannot be lazily
evaluated either:
pure int foo() { /*infinite loop */}
On Tuesday, 5 June 2018 at 17:47:15 UTC, Steven Schveighoffer
wrote:
Another observation: under the "infinite loops are important
observable behavior" world-view, pure functions cannot be
lazily evaluated either:
pure int foo() { /*infinite loop */}
void main(string[] args)
{
auto a =
On Tuesday, 5 June 2018 at 12:08:58 UTC, Simen Kjærås wrote:
There's a reason for those rules in the language, namely
function hijacking. This is an issue we take very seriously,
and workarounds exists.
So serious that there is no meaningful error message?
These issues can be ameliorated as
On Tuesday, June 05, 2018 15:09:56 Dejan Lekic via Digitalmars-d wrote:
> On Sunday, 3 June 2018 at 17:40:46 UTC, I love Ice Cream wrote:
> >> Is D really a top 20 language? I don't remember seeing it
> >> anywhere close to the top 20.
> >>
> >> https://www.tiobe.com/tiobe-index/ has them in 31
>
On Tuesday, 5 June 2018 at 19:05:27 UTC, DigitalDesigns wrote:
For loops HAVE a direct cpu semantic! Do you doubt this?
...
Right. If you're gonna keep running your mouth off. How about
looking at some disassembly then.
for(auto i=0; iUsing ldc -O4 -release for x86_64 processors, the
https://issues.dlang.org/show_bug.cgi?id=18945
ag0aep6g changed:
What|Removed |Added
CC||ag0ae...@gmail.com
--
On Tuesday, June 05, 2018 19:15:12 biocyberman via Digitalmars-d-announce
wrote:
> On Tuesday, 5 June 2018 at 11:09:31 UTC, Jonathan M Davis wrote:
> > [...]
>
> Very informative. I don't live in the US, but this gives me a
> feeling of how tough life can be over there for everyone, except
>
On 6/5/18 3:05 PM, DigitalDesigns wrote:
It's also often not necessary to be "as slow as possible". I'm not
asking for about generalities but specifics. It's great to make
generalizations about how things should be but I would like to know how
they are. Maybe in theory ranges could be more
On Tuesday, 5 June 2018 at 19:05:27 UTC, DigitalDesigns wrote:
For loops HAVE a direct cpu semantic! Do you doubt this?
What are they?
And for bonus points, are they actually used by compilers?
Then the final question: is the generated code any different than
inlined ranges?
On Tuesday, 5 June 2018 at 11:09:31 UTC, Jonathan M Davis wrote:
[...]
Very informative. I don't live in the US, but this gives me a
feeling of how tough life can be over there for everyone, except
lawyers.
On Tuesday, 5 June 2018 at 18:46:41 UTC, Timon Gehr wrote:
On 05.06.2018 18:50, DigitalDesigns wrote:
With a for loop, it is pretty much a wrapper on internal cpu
logic so it will be near as fast as possible.
This is not even close to being true for modern CPUs. There are
a lot of
On 05.06.2018 18:50, DigitalDesigns wrote:
With a for loop, it is pretty much a wrapper on internal cpu logic so it
will be near as fast as possible.
This is not even close to being true for modern CPUs. There are a lot of
architectural and micro-architectural details that affect performance
https://issues.dlang.org/show_bug.cgi?id=18470
github-bugzi...@puremagic.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.dlang.org/show_bug.cgi?id=18470
--- Comment #2 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/dlang/phobos
https://github.com/dlang/phobos/commit/b5162ecc014a33b5866f2de62b5af012cf425c1d
fix issue 18470 - std.algorithm.splitter has frame
I'm also having some issue now when I changed a type from using a
class to using it's base interface
Unhandled exception:
orange.serialization.SerializationException.SerializationException The object of the static type "const(ItemInterface)" have a different runtime type (Item) and therefore
On 6/5/18 12:10 PM, Stefan Koch wrote:
This is not bug just not very intuitive.
Since you are declaring a static array the value of n needs to known at
compiletime.
so it'll try to evaluate n at an compile-time context in which n is 1.
however when code-generation for the function is done
On 6/5/18 12:50 PM, DigitalDesigns wrote:
I suppose in the long run ranges do have the potential to out perform
since they do abstract but there is no guarantee they will even come
close. Having some "proof" that they are working well would ease my
mind. As this thread shows, ranges have some
On 6/5/18 10:48 AM, FeepingCreature wrote:
I'm just posting to clear up the misunderstanding that a call to a pure
function can be removed. Actually, even calls to strongly pure functions
cannot always be removed. This is because there is one thing that a pure
function can do that will change
On Saturday, 2 June 2018 at 20:11:17 UTC, Jacob Carlborg wrote:
On 2018-06-02 03:30, IntegratedDimensions wrote:
How can I modify the pre serialization and post serialization
values? I need to transform some variables that are stored but
I would like to do this easily "inline"(would be cool to
On Tuesday, 5 June 2018 at 13:33:18 UTC, Kagamin wrote:
Why message detection is in receiver instead of infrastructure?
Because recursion. One of the messages I've written is a wrapper
message for a multi-packet split message, and calls receive with
the reconstructed byte buffer. Fairly
On Tuesday, 5 June 2018 at 16:12:25 UTC, RalphBa wrote:
Did you ever have the need to write something efficient? .NET
is a sandbox for children and UX people.
Oh yeah, toy applications for children like StackOverflow,
Siemens NX, Solidworks, most of the Azure platform, MSSQL and
Visual
On Tue, Jun 05, 2018 at 06:55:42AM +, Joakim via Digitalmars-d-announce
wrote:
> On Tuesday, 5 June 2018 at 06:45:48 UTC, Adam Wilson wrote:
> > Hello Fellow D'ers,
> >
> > As some of you know I work for Microsoft. And as a result of the
> > recent acquisition of GitHub by Microsoft, I have
On Tuesday, 5 June 2018 at 14:48:23 UTC, FeepingCreature wrote:
I'm just posting to clear up the misunderstanding that a call
to a pure function can be removed. Actually, even calls to
strongly pure functions cannot always be removed. This is
because there is one thing that a pure function can
On Tuesday, 5 June 2018 at 13:05:56 UTC, Steven Schveighoffer
wrote:
On 6/4/18 5:52 PM, DigitalDesigns wrote:
On Monday, 4 June 2018 at 17:40:57 UTC, Dennis wrote:
On Monday, 4 June 2018 at 15:43:20 UTC, Steven Schveighoffer
wrote:
Note, it's not going to necessarily be as efficient, but
it's
On Tuesday, 5 June 2018 at 16:12:25 UTC, RalphBa wrote:
Of course it had to be losing money..how else would they have
convinced everyone it need to be aquired? That's long term Now
which company has done more for software development, besides
Microsoft?
GNU... oh sorry, you are speaking about
On Tuesday, 5 June 2018 at 11:35:10 UTC, Ethan wrote:
On Tuesday, 5 June 2018 at 10:11:49 UTC, Ethan wrote:
And, honestly, with this method, I am already seeing the
workaround. Because I've had to do it a ton of times already
with other templates. Run a search for 'mixin( "import' in
Binderoo
Of course it had to be losing money..how else would they have
convinced everyone it need to be aquired? That's long term Now
which company has done more for software development, besides
Microsoft?
GNU... oh sorry, you are speaking about companies... Sun... ok,
open and free software isn't
On Tuesday, 5 June 2018 at 13:27:35 UTC, Steven Schveighoffer
wrote:
On 6/5/18 6:40 AM, Simen Kjærås wrote:
On Tuesday, 5 June 2018 at 09:36:22 UTC, Gopan wrote:
void main()
{
immutable n = __ctfe ? 1 : 2;
int[n] a;
assert(a.length == n); // fails, wat
}
That's gotta be a bug -
https://issues.dlang.org/show_bug.cgi?id=18945
--- Comment #9 from David Bennett ---
(In reply to David Bennett from comment #8)
> (In reply to David Bennett from comment #7)
> > Then there are immutable struct members used at compile time, they might not
> > be easy to convert to an enum.
> >
On Tuesday, 5 June 2018 at 14:52:28 UTC, Timoses wrote:
Does `int[4] nums = void` work?
Work for what?
If you avoid initialization, then the variable(s) are not
initialized.
https://dlang.org/spec/declaration.html#void_init
However, an int is not nullable and always contains a value.
https://issues.dlang.org/show_bug.cgi?id=18945
--- Comment #8 from David Bennett ---
(In reply to David Bennett from comment #7)
> Then there are immutable struct members used at compile time, they might not
> be easy to convert to an enum.
> https://run.dlang.io/is/cfGfxw
> I've never seen it
https://issues.dlang.org/show_bug.cgi?id=18948
github-bugzi...@puremagic.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.dlang.org/show_bug.cgi?id=18948
--- Comment #1 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/dlang/phobos
https://github.com/dlang/phobos/commit/fa5830c32ee08c34bdfc10bfb62dd7cb5ee87ba3
Fix Issue 18948 - toLower and toUpper should work with
https://issues.dlang.org/show_bug.cgi?id=18945
--- Comment #7 from David Bennett ---
(In reply to Jonathan M Davis from comment #6)
>
> Just use an enum if you want the value to be known and used at compile time,
> and use an immutable variable if you want it to be known and used at
> runtime.
On Sunday, 3 June 2018 at 17:40:46 UTC, I love Ice Cream wrote:
Is D really a top 20 language? I don't remember seeing it
anywhere close to the top 20.
https://www.tiobe.com/tiobe-index/ has them in 31
Top comment is kind of depressing.
The right place to look is
On Saturday, 2 June 2018 at 18:10:38 UTC, eastanon wrote:
Does D array implementation support an array of null values?
int a[4] = null;
But I ran into a type error while checking if a[i] is null
foreach(i; 0..3){
if(i == null){
writeln("it is null");
}
}
}
How do you set fixed size
I'm just posting to clear up the misunderstanding that a call to
a pure function can be removed. Actually, even calls to strongly
pure functions cannot always be removed. This is because there is
one thing that a pure function can do that will change program
behavior if it is removed, even if
On Tuesday, 5 June 2018 at 10:11:49 UTC, Ethan wrote:
As soon as you have an overload of a function declared in the
base object you're mixing in to, any other overload mixed in
will not resolve correctly. Great.
Yes, it is great, since this lets you selectively override
behavior from a
On 06/04/2018 07:08 PM, Ethan wrote:
On Monday, 4 June 2018 at 18:11:47 UTC, Steven Schveighoffer wrote:
BTW, do you have cross-module inlining on?
Just to drive this point home.
https://run.dlang.io/is/nrdzb0
Manually implemented stride and fill with everything forced inline.
Otherwise,
05.06.2018 17:00, Steven Schveighoffer пишет:
To clarify a bit, complicated or controversial changes that are likely
to be delayed or stalled, should be split from simple doc changes if it
turns out it's not going to be pulled anytime soon. But normally, adding
fixes for docs I would think
On Tuesday, 5 June 2018 at 06:55:42 UTC, Joakim wrote:
On Tuesday, 5 June 2018 at 06:45:48 UTC, Adam Wilson wrote:
Hello Fellow D'ers,
As some of you know I work for Microsoft. And as a result of
the recent acquisition of GitHub by Microsoft, I have decided,
out of an abundance of caution,
On 6/5/18 9:58 AM, Steven Schveighoffer wrote:
On 6/5/18 3:20 AM, drug wrote:
04.06.2018 21:08, Steven Schveighoffer пишет:
On 6/4/18 1:51 PM, Joakim wrote:
On Monday, 4 June 2018 at 15:52:24 UTC, Steven Schveighoffer wrote:
On 6/2/18 3:23 AM, Mike Parker wrote:
[...]
I like the article,
https://issues.dlang.org/show_bug.cgi?id=18945
--- Comment #6 from Jonathan M Davis ---
(In reply to David Bennett from comment #4)
> I'm not sure what workaround we would recommend in the deprecation messaged
> as the current functionality is actually hard to replicate.
Just use an enum if you
On 6/5/18 3:20 AM, drug wrote:
04.06.2018 21:08, Steven Schveighoffer пишет:
On 6/4/18 1:51 PM, Joakim wrote:
On Monday, 4 June 2018 at 15:52:24 UTC, Steven Schveighoffer wrote:
On 6/2/18 3:23 AM, Mike Parker wrote:
[...]
I like the article, but was taken aback a bit by this quote: "for
On Tue, Jun 5, 2018 at 3:54 PM, Steven Schveighoffer via
Digitalmars-d-announce wrote:
> On 6/5/18 3:25 AM, Brian wrote:
>
> source code in github https://github.com/huntlabs/hunt/
>> documents in wiki https://github.com/huntlabs/hunt/wiki/
>> hunt framework website http://www.huntframework.com/
On 6/5/18 3:25 AM, Brian wrote:
source code in github https://github.com/huntlabs/hunt/
documents in wiki https://github.com/huntlabs/hunt/wiki/
hunt framework website http://www.huntframework.com/
Is there a way to view your website in English? I found a popup on the
bottom that has
https://issues.dlang.org/show_bug.cgi?id=18945
anonymous4 changed:
What|Removed |Added
Hardware|x86 |All
OS|Windows
On Sunday, 3 June 2018 at 16:25:29 UTC, Ethan wrote:
Step seven: In your receive function that takes a byte stream,
put in a switch statement that looks a little bit like the
following:
switch( msg.GetID )
{
static foreach( Message; ServerMessages )
{
case ObjectIDOf!Message:
On 6/5/18 6:40 AM, Simen Kjærås wrote:
On Tuesday, 5 June 2018 at 09:36:22 UTC, Gopan wrote:
void main()
{
immutable n = __ctfe ? 1 : 2;
int[n] a;
assert(a.length == n); // fails, wat
}
That's gotta be a bug - that should give a 'variable n cannot be read at
compile time' error.
https://issues.dlang.org/show_bug.cgi?id=18948
Issue ID: 18948
Summary: std.uni.toLower and std.uni.toUpper should work with
random access ranges
Product: D
Version: D2
Hardware: All
OS: All
https://issues.dlang.org/show_bug.cgi?id=18947
Issue ID: 18947
Summary: No way to get list of overloads from template mixins
Product: D
Version: D2
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
On 6/4/18 5:52 PM, DigitalDesigns wrote:
On Monday, 4 June 2018 at 17:40:57 UTC, Dennis wrote:
On Monday, 4 June 2018 at 15:43:20 UTC, Steven Schveighoffer wrote:
Note, it's not going to necessarily be as efficient, but it's likely
to be close.
-Steve
I've compared the range versions with
On Tuesday, 5 June 2018 at 07:25:33 UTC, Brian wrote:
We are pleased to announce an official version of hunt 1.0 ,
This is an important milestone release!
[...]
/usr/bin/ld: cannot find -lmysqlclient
collect2: error: ld returned 1 exit status
Error: linker exited with status 1
https://issues.dlang.org/show_bug.cgi?id=18946
Shachar Shemesh changed:
What|Removed |Added
CC||shac...@weka.io
--
On Tuesday, 5 June 2018 at 09:58:43 UTC, Nicholas Wilson wrote:
prints
Exception
https://issues.dlang.org/show_bug.cgi?id=18946
https://issues.dlang.org/show_bug.cgi?id=18945
David Bennett changed:
What|Removed |Added
CC||davidbenn...@bravevision.co
https://issues.dlang.org/show_bug.cgi?id=18946
Issue ID: 18946
Summary: assert message can throw hijacking the assert failure.
Product: D
Version: D2
Hardware: x86
OS: Mac OS X
Status: NEW
Severity:
https://issues.dlang.org/show_bug.cgi?id=18945
--- Comment #3 from Jonathan M Davis ---
This probably does need to be removed via deprecation rather than simply making
it an error, but allowing it is exactly the sort of thing that increases the
confusion about how CTFE works and when it's used.
On Tuesday, 5 June 2018 at 10:11:49 UTC, Ethan wrote:
Exhibit A: https://run.dlang.io/is/a85Lbq
I submitted a bug with the above code, and it was "helpfully"
shut down with a link to the documentation and workaround.
Congratulations. That's not the use case here, and to be quite
honest this
https://issues.dlang.org/show_bug.cgi?id=18945
--- Comment #2 from David Bennett ---
Disclaimer: Just a D user, I hold no decision making power or insight into the
history here.
const and immutable are runtime lvalues that have a known way to get "a" value
at compiletime. As you have noticed
On Monday, 4 June 2018 at 20:00:45 UTC, Maksim Fomin wrote:
Just as rough estimate: to support $7.5 bl valuation Microsoft
must turn -$30 ml. net loss company into business generating
around $750 ml. for many years. There is no way to get these
money from the market. Alternatively, the project
On Tuesday, 5 June 2018 at 10:11:49 UTC, Ethan wrote:
And, honestly, with this method, I am already seeing the
workaround. Because I've had to do it a ton of times already
with other templates. Run a search for 'mixin( "import' in
Binderoo to see how many times I've had to get around the
https://issues.dlang.org/show_bug.cgi?id=18945
Jonathan M Davis changed:
What|Removed |Added
CC||issues.dl...@jmdavisprog.co
On Tuesday, June 05, 2018 11:18:05 Gopan via Digitalmars-d-learn wrote:
> On Tuesday, 5 June 2018 at 10:40:20 UTC, Simen Kjærås wrote:
> > On Tuesday, 5 June 2018 at 09:36:22 UTC, Gopan wrote:
> >> void main()
> >> {
> >>
> >> immutable n = __ctfe ? 1 : 2;
> >> int[n] a;
> >>
On Tuesday, 5 June 2018 at 10:40:20 UTC, Simen Kjærås wrote:
On Tuesday, 5 June 2018 at 09:36:22 UTC, Gopan wrote:
void main()
{
immutable n = __ctfe ? 1 : 2;
int[n] a;
assert(a.length == n); // fails, wat
}
That's gotta be a bug - that should give a 'variable n cannot
be read at
On Tuesday, 5 June 2018 at 03:53:31 UTC, Adam Wilson wrote:
GitHub has not been profitable for years and is thought to have
had cash reserves for only one or two more months of
operations. Losing GitHub entirely overnight would have been an
unmitigated disaster for the entire Open-Source
On Tuesday, June 05, 2018 10:34:54 ExportThis via Digitalmars-d-announce
wrote:
> On Tuesday, 5 June 2018 at 06:55:42 UTC, Joakim wrote:
> > This reads like a joke, why would it matter if you contributed
> > to open source projects on an open platform that your employer
> > runs?
>
> If you read
On Tuesday, 5 June 2018 at 10:11:49 UTC, Ethan wrote:
Exhibit A: https://run.dlang.io/is/a85Lbq
[..snip..]
I submitted a bug with the above code, and it was "helpfully"
shut down with a link to the documentation and workaround.
This looks like the bug report you are referring to:
On Monday, 4 June 2018 at 19:06:52 UTC, Maksim Fomin wrote:
My second reaction after reading news (after shock) was to
visit D forum.
Same here! I was off for a few days and found out today on GitHub
[1], and then I remembered the thread header talking about
GitLab. I'm skeptical to say
On Tuesday, 5 June 2018 at 09:36:22 UTC, Gopan wrote:
void main()
{
immutable n = __ctfe ? 1 : 2;
int[n] a;
assert(a.length == n); // fails, wat
}
That's gotta be a bug - that should give a 'variable n cannot be
read at compile time' error. The fact that n is immutable
shouldn't
https://issues.dlang.org/show_bug.cgi?id=18945
Issue ID: 18945
Summary: immutable variable is used as if it's an enum
Product: D
Version: D2
Hardware: x86
OS: Windows
Status: NEW
Keywords: CTFE
On Tuesday, 5 June 2018 at 06:55:42 UTC, Joakim wrote:
This reads like a joke, why would it matter if you contributed
to open source projects on an open platform that your employer
runs?
If you read between the lines, you can 'kinda' get the message.
A Microsoft employee.
A Microsoft
https://issues.dlang.org/show_bug.cgi?id=6447
Russel Winder changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|WORKSFORME
I've come across this before with Binderoo, but now I've got
really simple use cases.
Rather than having one unmaintainable mess of a file that handles
everything (for a really egregious example, see
std.datetime.systime which has the distinction of both its source
code and documentation
On Tuesday, 5 June 2018 at 09:03:03 UTC, Simen Kjærås wrote:
On Tuesday, 5 June 2018 at 08:26:22 UTC, Nicholas Wilson wrote:
writeln("Assert"); // this is not caught because the thrown
throwable is not an exception
Now that's plain false - If you replace the call to
throwingFunc() with a
https://issues.dlang.org/show_bug.cgi?id=18936
--- Comment #2 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/dlang/dmd
https://github.com/dlang/dmd/commit/d2884aa5a06f59ec6f4c4ae48ef864037c4d238f
fix Issue 18936 - Internal error: dmd/backend/cgxmm.c 684
https://issues.dlang.org/show_bug.cgi?id=18936
github-bugzi...@puremagic.com changed:
What|Removed |Added
Status|NEW |RESOLVED
On Sunday, 3 June 2018 at 21:32:06 UTC, gdelazzari wrote:
Couldn't a keyword like "ctfe" (just making it up right now)
exist? So that, when seeing something like
ctfe myNumber = 5;
ctfe if (myNumber + 2 == 7)
{
// ...
}
one could immediately understand that the code is
executed/evaluated
1 - 100 of 130 matches
Mail list logo
