On Tuesday, 15 May 2018 at 21:25:05 UTC, Andrei Alexandrescu
wrote:
Hello, I was reviewing again DIP 1011 and investigated a
library solution. That led to
https://gist.github.com/run-dlang/18845c9df3d73e45c945feaccfebfcdc
It builds on the opening examples in:
https://github.com/dlang/DIPs/blo
On Thursday, 17 May 2018 at 06:03:19 UTC, arturg wrote:
you could declare the public api of your class inside an actual
interface then use it instead of the class, that wont give you
access to the private members of the class.
you mean like this?
module test;
interface
On Thursday, 17 May 2018 at 07:30:58 UTC, KingJoffrey wrote:
On Thursday, 17 May 2018 at 06:03:19 UTC, arturg wrote:
you could declare the public api of your class inside an
actual interface then use it instead of the class, that wont
give you access to the private members of the class.
you
Any custom modification swill overwrite the original sc.ini file.
The compiler should copy(rename) or create the file on demand
when it is ran and does not exist in the same path as the
compiler.
This way one can unzip over a previous install without losing the
original sc.ini file. It is a p
On Thursday, 17 May 2018 at 07:36:40 UTC, arturg wrote:
no, that uses type inferance.
you have to do
Animal dog = new Dog;
i tried it... certainly interesting.. thanks.
but, I don't recall in my opening post, saying I'm ok with having
to create an interface for every class I create, just so
On Thursday, 17 May 2018 at 08:12:50 UTC, Mike Parker wrote:
This is the review thread for the first Community Review round
for DIP 1014, "Hooking D's struct move semantics".
And the link to the DIP:
https://github.com/dlang/DIPs/blob/38cec74a7471735559e3b8a7553f55102d289d28/DIPs/DIP1014.md
This is the review thread for the first Community Review round
for DIP 1014, "Hooking D's struct move semantics".
All review-related feedback on and discussion of the DIP should
occur in this thread. The review period will end at 11:59 PM ET
on May 31, or when I make a post declaring it comple
On 17/05/2018 8:12 PM, Mike Parker wrote:
This is the review thread for the first Community Review round for DIP
1014, "Hooking D's struct move semantics".
All review-related feedback on and discussion of the DIP should occur in
this thread. The review period will end at 11:59 PM ET on May 31,
On Monday, 19 September 2016 at 22:59:53 UTC, Jonathan Marler
wrote:
On Monday, 19 September 2016 at 22:17:34 UTC, Mathias Lang
wrote:
2016-09-19 23:18 GMT+02:00 Jonathan Marler via Digitalmars-d <
digitalmars-d@puremagic.com>:
[...]
No you can't. The example is wrong, but Stefan is right.
On Thursday, 17 May 2018 at 07:38:50 UTC, IntegratedDimensions
wrote:
This way one can unzip over a previous install without losing
the original sc.ini file. It is a pain to have to remember to
back it up every time(given if one updates slowly).
You only need to back it up once.
That or simpl
On 17/05/2018 8:50 PM, Chris wrote:
For what it's worth, I came across this website:
https://benchmarksgame-team.pages.debian.net/benchmarksgame/
D is not there. Anyone interested, if it's worth it?
It isn't happening /thread.
On Thursday, 17 May 2018 at 07:38:50 UTC, IntegratedDimensions
wrote:
Any custom modification swill overwrite the original sc.ini
file. The compiler should copy(rename) or create the file on
demand when it is ran and does not exist in the same path as
the compiler.
Not detracting from your ar
On Thursday, 17 May 2018 at 07:38:50 UTC, IntegratedDimensions
wrote:
This way one can unzip over a previous install without losing
the original sc.ini file.
Also that's not a correct way to update, you should unzip into an
empty folder or stray files can be left from the previous
installatio
For what it's worth, I came across this website:
https://benchmarksgame-team.pages.debian.net/benchmarksgame/
D is not there. Anyone interested, if it's worth it?
On Thursday, 17 May 2018 at 08:51:39 UTC, rikki cattermole wrote:
On 17/05/2018 8:50 PM, Chris wrote:
For what it's worth, I came across this website:
https://benchmarksgame-team.pages.debian.net/benchmarksgame/
D is not there. Anyone interested, if it's worth it?
It isn't happening /thread.
On 17/05/2018 8:52 PM, ixid wrote:
On Thursday, 17 May 2018 at 08:51:39 UTC, rikki cattermole wrote:
On 17/05/2018 8:50 PM, Chris wrote:
For what it's worth, I came across this website:
https://benchmarksgame-team.pages.debian.net/benchmarksgame/
D is not there. Anyone interested, if it's wor
On Thursday, 17 May 2018 at 02:32:07 UTC, KingJoffrey wrote:
I propose an idea, for discussion (robust discussion even
better ;-)
Add an new attribute to class, named 'sealed'.
If class level protection is added, please do not call it sealed.
People from c++ might be suprised by 'private' alr
On 17/05/18 11:22, rikki cattermole wrote:
What is the benefit of opPostMove over copy constructors (not postblit)?
The two are unrelated. A copy is a very different operation from a move.
With a copy, you have to figure out how to duplicate the resources used
by the object. With a move, no
On Thursday, 17 May 2018 at 10:34:18 UTC, Zoadian wrote:
On Thursday, 17 May 2018 at 02:32:07 UTC, KingJoffrey wrote:
I propose an idea, for discussion (robust discussion even
better ;-)
Add an new attribute to class, named 'sealed'.
If class level protection is added, please do not call it
3. When deciding to move a struct instance, the compiler MUST
emit a call to the struct's __move_post_blt after blitting the
instance and before releasing the memory containing the old
instance. __move_post_blt MUST receive references to both the
pre- and post-move instances.
This implies tha
On Monday, 30 April 2018 at 21:11:07 UTC, Gerald wrote:
I'll freely admit I haven't put a ton of thought into this post
(never a good start), however I'm genuinely curious what
people's feeling are with regards to the auto keyword.
I prefer types spelled as it helps to understand the code. In
On Thursday, 17 May 2018 at 02:32:07 UTC, KingJoffrey wrote:
I propose an idea, for discussion (robust discussion even
better ;-)
Add an new attribute to class, named 'sealed'.
No, not sealed as in Scala.
No, not sealed as in C#
sealed as in oxford dictionary (close securely, non-porous).
w
On Thursday, 17 May 2018 at 11:56:51 UTC, Piotr Mitana wrote:
My opinion is that it's not worth a new keyword and time for
implementing. In the same manner you could ask for removing
friend concept from C++ as a bad concept. I don't answer the
question whether this concept is good or bad - ju
I'm not sure I follow all of your comments.
For the rest my comments, let's assume that the compiler may assume that
__move_post_blt is a no-op if hasElaborateMove returns false.
On 17/05/18 14:33, kinke wrote:
3. When deciding to move a struct instance, the compiler MUST emit a
call to the s
On Thursday, 17 May 2018 at 09:26:34 UTC, rikki cattermole wrote:
On 17/05/2018 8:52 PM, ixid wrote:
On Thursday, 17 May 2018 at 08:51:39 UTC, rikki cattermole
wrote:
On 17/05/2018 8:50 PM, Chris wrote:
For what it's worth, I came across this website:
https://benchmarksgame-team.pages.debian.
On Thursday, 17 May 2018 at 05:01:54 UTC, Joakim wrote:
On Wednesday, 16 May 2018 at 20:11:35 UTC, Andrei Alexandrescu
wrote:
On 5/16/18 1:18 PM, Joakim wrote:
On Wednesday, 16 May 2018 at 16:48:28 UTC, Dmitry Olshansky
wrote:
On Wednesday, 16 May 2018 at 15:48:09 UTC, Joakim wrote:
On Wednesd
On Thursday, 17 May 2018 at 11:18:52 UTC, KingJoffrey wrote:
On Thursday, 17 May 2018 at 10:34:18 UTC, Zoadian wrote:
On Thursday, 17 May 2018 at 02:32:07 UTC, KingJoffrey wrote:
[...]
People from c++ might be suprised by 'private' already. We do
not have to confuse those c#ies too.
Interest
On 5/16/18 10:32 PM, KingJoffrey wrote:
I propose an idea, for discussion (robust discussion even better ;-)
Add an new attribute to class, named 'sealed'.
No, not sealed as in Scala.
No, not sealed as in C#
sealed as in oxford dictionary (close securely, non-porous).
when sealed is applied
On Thursday, 17 May 2018 at 11:56:51 UTC, Piotr Mitana wrote:
To sum up [TLDR]: I don't see your arguments strong enough to
alter the language (especially make a cross-language confusion
over the "sealed" keyword), but DScaner check would still allow
to track down what you consider bad.
'al
On Thursday, 17 May 2018 at 13:28:19 UTC, Steven Schveighoffer
wrote:
Essentially, if you put your class you want "sealed" into it's
own module, and then publicly import the module from the API
module, you will get the same effect. This is even easier now
with the package module than it used
Looks like requirement for @nogc @safe has no consequence as the
DIP suggests to infer them anyway. On ideological side safety
can't be a requirement because it would contradict its purpose of
providing guarantee. Especially if the suggested use case is
handling of dangling pointers.
On 17/05/18 16:42, Kagamin wrote:
Looks like requirement for @nogc @safe has no consequence as the DIP
suggests to infer them anyway. On ideological side safety can't be a
requirement because it would contradict its purpose of providing
guarantee.
I think you are confusing __move_post_blt's i
On 5/17/18 9:38 AM, KingJoffrey wrote:
On Thursday, 17 May 2018 at 13:28:19 UTC, Steven Schveighoffer wrote:
Essentially, if you put your class you want "sealed" into it's own
module, and then publicly import the module from the API module, you
will get the same effect. This is even easier no
On Thu, 2018-05-17 at 12:51 +, Chris M. via Digitalmars-d wrote:
[…]
> He'll probably pop up and confirm for us since he somehow always
> knows when we bring this up
He has (had?) robot listeners trawling the various email collectors which
would then let him know the Benchmarks Game was being
On 05/15/2018 08:44 PM, Jonathan Marler wrote:
On Tuesday, 15 May 2018 at 21:25:05 UTC, Andrei Alexandrescu wrote:
Hello, I was reviewing again DIP 1011 and investigated a library
solution. That led to
https://gist.github.com/run-dlang/18845c9df3d73e45c945feaccfebfcdc
It builds on the opening
On Thursday, 17 May 2018 at 13:14:46 UTC, Patrick Schluter wrote:
This is not practical, sorry. What happens when your message
loses the header? Exactly, the rest of the message is garbled.
Why would it lose the header? TCP guarantees delivery and
checksums the data, that's effective enough at
On Thursday, 17 May 2018 at 12:36:29 UTC, Shachar Shemesh wrote:
Again, as far as I know, structs are not copied when passed as
arguments. They are allocated on the caller's stack and a
reference is passed to the callee. If that's the case, no move
(of any kind) is done.
That's the exception
On 05/17/2018 04:50 AM, Chris wrote:
For what it's worth, I came across this website:
https://benchmarksgame-team.pages.debian.net/benchmarksgame/
D is not there. Anyone interested, if it's worth it?
It would be well worth the effort.
On 05/17/2018 09:14 AM, Patrick Schluter wrote:
I'm in charge at the European Commission of the biggest translation
memory in the world.
Impressive! Is that the Europarl?
On Thursday, 17 May 2018 at 15:23:50 UTC, kinke wrote:
See IR for https://run.dlang.io/is/1JIsk7.
I should probably emphasize that the LLVM `byval` attribute is
strange at first sight. Pseudo-IR `void foo(S* byval param); ...
foo(S* byarg arg);` doesn't mean that the IR callee gets the S*
po
On Thursday, 17 May 2018 at 13:50:26 UTC, Shachar Shemesh wrote:
There is no such use case. Please remember that at the time
opPostMove is called, both new and old memory are still
allocated.
That's an interesting moment too. A struct that was supposed to
be moved is copied instead and exists
On Wednesday, 16 May 2018 at 19:16:11 UTC, Manu wrote:
I'm wondering if it should also be possible to apply in/out
contracts
to function prototypes?
Contracts should be checked by the caller, yes, and the idea
regularly pops up here, I though there's an issue for this, but
can't find it, may
On Thursday, 17 May 2018 at 07:58:55 UTC, KingJoffrey wrote:
Remember, the idea for discussion is about adding one single
attribute 'sealed' to the class - the discussion is a lot less
about 'how can we prevent having to add a this new attribute'.
It is normal, whenever someone suggests changi
On 5/16/2018 10:01 PM, Joakim wrote:
Unicode was a standardization of all the existing code pages and then added
these new transfer formats, but I have long thought that they'd have been better
off going with a header-based format that kept most languages in a single-byte
scheme, as they mostly
On Thursday, 17 May 2018 at 17:16:03 UTC, Walter Bright wrote:
On 5/16/2018 10:01 PM, Joakim wrote:
Unicode was a standardization of all the existing code pages
and then added these new transfer formats, but I have long
thought that they'd have been better off going with a
header-based format
On Thursday, 17 May 2018 at 09:26:34 UTC, rikki cattermole wrote:
On 17/05/2018 8:52 PM, ixid wrote:
On Thursday, 17 May 2018 at 08:51:39 UTC, rikki cattermole
wrote:
On 17/05/2018 8:50 PM, Chris wrote:
For what it's worth, I came across this website:
https://benchmarksgame-team.pages.debian.
On Thursday, 17 May 2018 at 15:37:01 UTC, Andrei Alexandrescu
wrote:
On 05/17/2018 09:14 AM, Patrick Schluter wrote:
I'm in charge at the European Commission of the biggest
translation memory in the world.
Impressive! Is that the Europarl?
No, Euramis. The central translation memory develope
On Thursday, 17 May 2018 at 17:16:03 UTC, Walter Bright wrote:
On 5/16/2018 10:01 PM, Joakim wrote:
Unicode was a standardization of all the existing code pages
and then added these new transfer formats, but I have long
thought that they'd have been better off going with a
header-based format
On Thu, May 17, 2018 at 10:16:03AM -0700, Walter Bright via Digitalmars-d wrote:
> On 5/16/2018 10:01 PM, Joakim wrote:
> > Unicode was a standardization of all the existing code pages and
> > then added these new transfer formats, but I have long thought that
> > they'd have been better off going
On Thursday, 17 May 2018 at 15:16:19 UTC, Joakim wrote:
On Thursday, 17 May 2018 at 13:14:46 UTC, Patrick Schluter
wrote:
This is not practical, sorry. What happens when your message
loses the header? Exactly, the rest of the message is garbled.
Why would it lose the header? TCP guarantees del
On 17/05/18 18:47, kinke wrote:
On Thursday, 17 May 2018 at 15:23:50 UTC, kinke wrote:
See IR for https://run.dlang.io/is/1JIsk7.
I should probably emphasize that the LLVM `byval` attribute is strange
at first sight. Pseudo-IR `void foo(S* byval param); ... foo(S* byarg
arg);` doesn't mean t
On Thursday, 17 May 2018 at 08:37:01 UTC, Heromyth wrote:
On Monday, 19 September 2016 at 22:59:53 UTC, Jonathan Marler
wrote:
On Monday, 19 September 2016 at 22:17:34 UTC, Mathias Lang
wrote:
[...]
Good example, thanks for the information.
Maybe the compiler can do more works to make the c
On 17/05/18 19:08, Kagamin wrote:
On Thursday, 17 May 2018 at 13:50:26 UTC, Shachar Shemesh wrote:
There is no such use case. Please remember that at the time opPostMove
is called, both new and old memory are still allocated.
That's an interesting moment too. A struct that was supposed to be m
On 17 May 2018 at 01:12, Mike Parker via Digitalmars-d
wrote:
> This is the review thread for the first Community Review round for DIP 1014,
> "Hooking D's struct move semantics".
>
> All review-related feedback on and discussion of the DIP should occur in
> this thread. The review period will end
This strange code - https://run.dlang.io/is/BKgv49 - fails with
error "Error: constructor calls not allowed in loops or after
labels", but there is no loops or labels.
On 5/17/18 3:55 PM, DarkHole wrote:
This strange code - https://run.dlang.io/is/BKgv49 - fails with error
"Error: constructor calls not allowed in loops or after labels", but
there is no loops or labels.
Switch cases are labels.
-Steve
On 5/17/18 4:02 PM, Steven Schveighoffer wrote:
On 5/17/18 3:55 PM, DarkHole wrote:
This strange code - https://run.dlang.io/is/BKgv49 - fails with error
"Error: constructor calls not allowed in loops or after labels", but
there is no loops or labels.
Switch cases are labels.
That being sai
On 17/05/18 22:29, Manu wrote:
This is great!
I've wanted this on numerous occasions when interacting with C++ code.
This will make interaction more complete.
Within self-contained D code, I have avoided self-pointers by using
self-offsets instead in the past (a bit hack-ey). But this nicely
ti
On Thursday, 17 May 2018 at 20:02:19 UTC, Steven Schveighoffer
wrote:
On 5/17/18 3:55 PM, DarkHole wrote:
This strange code - https://run.dlang.io/is/BKgv49 - fails
with error "Error: constructor calls not allowed in loops or
after labels", but there is no loops or labels.
Switch cases are la
On 5/17/18 4:25 PM, DarkHole wrote:
On Thursday, 17 May 2018 at 20:02:19 UTC, Steven Schveighoffer wrote:
On 5/17/18 3:55 PM, DarkHole wrote:
This strange code - https://run.dlang.io/is/BKgv49 - fails with error
"Error: constructor calls not allowed in loops or after labels", but
there is no l
On Thursday, 17 May 2018 at 17:26:04 UTC, Dmitry Olshansky wrote:
TCP being reliable just plain doesn’t cut it. Corruption of
single bit is very real.
Quoting to highlight and agree.
TCP is reliable because it resends dropped packets and delivers
them in order.
I don't write TCP packets to
On Thu, May 17, 2018 at 07:13:23PM +, Patrick Schluter via Digitalmars-d
wrote:
[...]
> - the auto-synchronization and the statelessness are big deals.
Yes. Imagine if we standardized on a header-based string encoding, and
we wanted to implement a substring function over a string that contai
And at the risk of getting this topic back on track:
On Wednesday, 16 May 2018 at 20:34:26 UTC, Walter Bright wrote:
Linkers already do that. Alignment is specified on all symbols
emitted by the compiler, and the linker uses that info.
Mea culpa. Upon further thinking, two things strike me:
1
On Thursday, 17 May 2018 at 08:53:06 UTC, Vladimir Panteleev
wrote:
On Thursday, 17 May 2018 at 07:38:50 UTC, IntegratedDimensions
wrote:
Any custom modification swill overwrite the original sc.ini
file. The compiler should copy(rename) or create the file on
demand when it is ran and does not e
On Friday, 18 May 2018 at 00:05:49 UTC, IntegratedDimensions
wrote:
This may be a suitable solution. While it has some overhead and
pollutes the environment, it at least offers a working
alternative unlike other (non)"solutions".
It would be better if HOME wasn't so general since other
applic
On Thursday, 17 May 2018 at 14:14:28 UTC, Steven Schveighoffer
wrote:
D's main draw is not OOP. So if you are here for OOP goodies,
then you are definitely better off looking elsewhere.
I'll add that too my list of D forum quotes.
That being said, D does have OOP, and many OOP programmers
On 17 May 2018 at 13:25, Shachar Shemesh via Digitalmars-d
wrote:
> On 17/05/18 22:29, Manu wrote:
>>
>>
>> This is great!
>> I've wanted this on numerous occasions when interacting with C++ code.
>> This will make interaction more complete.
>>
>> Within self-contained D code, I have avoided self-
On Thursday, May 17, 2018 08:51:34 Kagamin via Digitalmars-d wrote:
> On Thursday, 17 May 2018 at 07:38:50 UTC, IntegratedDimensions
>
> wrote:
> > This way one can unzip over a previous install without losing
> > the original sc.ini file.
>
> Also that's not a correct way to update, you should unz
Has this been implemented in DMD master?
So I was looking at the changelog[1] and tried to build the
example, but it erred.
https://github.com/dlang/dmd/blob/master/changelog/expression-based_contract_syntax.dd
On Thursday, 17 May 2018 at 23:16:03 UTC, H. S. Teoh wrote:
On Thu, May 17, 2018 at 07:13:23PM +, Patrick Schluter via
Digitalmars-d wrote: [...]
[...]
Yes. Imagine if we standardized on a header-based string
encoding, and we wanted to implement a substring function over
a string that c
==
log:
==
[majestio@freebsd ~/Projects/webapp]$ dub
Performing "debug" build using /usr/local/bin/dmd for x86_64.
taggedalgebraic 0.10.11: target for configuration "library" is
On Friday, 18 May 2018 at 05:28:10 UTC, Arun Chandrasekaran wrote:
Has this been implemented in DMD master?
So I was looking at the changelog[1] and tried to build the
example, but it erred.
https://github.com/dlang/dmd/blob/master/changelog/expression-based_contract_syntax.dd
https://githu
On Friday, 18 May 2018 at 05:44:12 UTC, Majestio wrote:
==
log:
==
[majestio@freebsd ~/Projects/webapp]$ dub
Performing "debug" build using /usr/local/bin/dmd for x86_64.
tagge
73 matches
Mail list logo
