On Wednesday, 28 August 2024 at 12:55:35 UTC, Mike Shah wrote:
I do like @live, curious others thoughts? Perhaps it doesn't
need to be an attribute though and is instead a compiler flag
for an analysis pass on any function (kind of reminds me of
frameworks like Soot for Java that you control va
On Wednesday, 28 February 2024 at 03:28:01 UTC, Mike Parker wrote:
After discussion in a recent meeting, we're ready now to start
accepting DIPs for review. And that means it's time to announce
the new process.
Very excited to see this. I've already submitted my own DIP idea
to get the ball r
On Tuesday, 14 November 2023 at 15:05:34 UTC, Steven
Schveighoffer wrote:
When considering how this should work, I would strongly suggest
it be the default to work with the current edition of the
language. Nobody wants to always have to attribute their module
(or whatever other opt-in mechanism
On Monday, 13 November 2023 at 16:23:05 UTC, Tim wrote:
The visitor can already be `extern(D)`. Only member functions
overriding those in the base class need to be `extern(C++)`.
Other member functions can then use paratemers, which would be
incompatible with `extern(C++)`.
Wow, it really was
On Monday, 13 November 2023 at 10:01:23 UTC, RazvanN wrote:
On Sunday, 12 November 2023 at 21:55:31 UTC, Paul Backus wrote:
I have no use for overriding AST nodes, but the ability to use
`extern(D)` visitors with dmd-as-a-library would be a welcome
improvement.
I have already brought that up
On Sunday, 12 November 2023 at 19:50:02 UTC, Mike Parker wrote:
https://gist.github.com/mdparker/f28c9ae64f096cd06db6b987318cc581
There was a side discussion about how the `extern(C++)`
interface affects dmd-as-a-library.
Personally, my number-one complaint with dmd-as-a-library is that
I a
On Thursday, 13 July 2023 at 14:00:49 UTC, Mike Parker wrote:
Finally, I told everyone about a conversation I'd had with
someone who was planning to submit a proposal to add slices to
C. Walter was happy to hear about that, as he had been
informally pushing for that for years. He talked about h
On Thursday, 11 May 2023 at 13:31:58 UTC, Steven Schveighoffer
wrote:
On 5/10/23 11:22 PM, Paul Backus wrote:
In fact, for this particular example, there are actually two
enums in the DMD source code that these symbols could be
coming from: `enum TargetOS` in `cli.d`, and `enum OS` in
`target.
On Thursday, 11 May 2023 at 00:56:03 UTC, ryuukk_ wrote:
Don't you find this code easier to read and review?
```D
if (target.os == .Windows)
{
item("windows");
}
else
{
item("posix");
if (target.os == .linux)
On Sunday, 7 May 2023 at 02:15:02 UTC, monkyyy wrote:
On Wednesday, 3 May 2023 at 11:13:34 UTC, Mike Parker wrote:
IVY, their organizational development program
Your solution to hearing luas dev saying "I dont manage
anything" and whatever feedback from your survey, is you got
corporate trai
On Tuesday, 25 April 2023 at 04:54:43 UTC, Mike Parker wrote:
I submitted DIP1044, "Enum Type Inference", to Walter and Atila
on April 1. I received the final decision from them on April
18. They have decided not to accept this proposal.
IMO this is the correct decision. While a feature like t
On Saturday, 28 January 2023 at 13:04:33 UTC, Johan wrote:
Is there a document describing cases where removal of
`@property` does not lead to an error but does lead to a change
in behavior of code?
We are considering a blanket removal of 3000+ instances of
`@property`. The resulting compile e
On Friday, 26 August 2022 at 11:39:53 UTC, Andrey Zherikov wrote:
On Friday, 19 August 2022 at 11:36:09 UTC, Iain Buclaw wrote:
GCC version 12.2 has been released.
Is it possible to add GDC to [github
actions](https://github.com/dlang-community/setup-dlang)?
There is some discussion here:
On Saturday, 25 June 2022 at 01:50:32 UTC, zjh wrote:
On Friday, 24 June 2022 at 14:27:17 UTC, Mike Parker wrote:
...
I think there should be a more detailed introduction to `'DMD'`.
The best introduction is probably Walter Bright's DConf 2016
talk, "Spelunking D Compiler Internals":
htt
On Friday, 24 June 2022 at 14:27:17 UTC, Mike Parker wrote:
The monthly meeting for June 2022 took place on June 10.
Just want to say, thanks for writing up these summaries every
month. I'm sure it's not the most exciting work, but the
transparency is very much appreciated.
On Sunday, 29 May 2022 at 07:43:20 UTC, Carsten Schlote wrote:
Source: https://gitlab.com/carsten.schlote/xxhash3
Dub Code: https://code.dlang.org/packages/xxhash3
[...]
Optimized code already outperforms the phobos built-in digest
types. See the benchmarks reported by tool at
https://gitla
On Sunday, 27 February 2022 at 11:53:18 UTC, Mike Parker wrote:
**ImportC**
Walter told us how he thinks ImportC is going to be a big deal
for D. He wants to get us "over the hump" with getting it
working properly. He thinks his C extension to allow importing
D files in C is working out far be
On Thursday, 24 February 2022 at 13:05:33 UTC, Mike Parker wrote:
In January, I announced that we were looking to fill the vacant
Pull-Request and Issue Manager position sponsored by Symmetry
Investments. We received some applications, Symmetry evaluated
them, and we agreed on a candidate we be
On Saturday, 19 February 2022 at 20:26:45 UTC, Elronnd wrote:
On Saturday, 19 February 2022 at 17:33:07 UTC, matheus wrote:
By the way English isn't my first language but I think there
is a small typo:
"In D, such nuances are fewer, for header files are not
required."
I think it's missing t
On Wednesday, 9 February 2022 at 14:30:30 UTC, Guillaume Piolat
wrote:
On Monday, 7 February 2022 at 19:57:28 UTC, forkit wrote:
First, I'm not 'insisting' on anything. I'm just expressing a
view.
nodiscard is already used by more programmers that D is likely
to ever adopt.
Indeed, it's the
On Monday, 7 February 2022 at 23:40:38 UTC, Walter Bright wrote:
On 2/6/2022 9:05 PM, forkit wrote:
only to have the compiler complain, that its' actually @mustUse
I have to agree. All D keywords and imports and
compiler-recognized attributes are lower case, @mustuse should
be consistent wit
On Monday, 7 February 2022 at 05:12:39 UTC, forkit wrote:
no amount of replies will change anything ;-)
.. people will still 'think' @nodiscard, but have to 'remember'
it's actually @mustuse, but oops.. no... it's @mustUse..
I do not expect anything from my feedback ;-) .. I'm just
saying..
On Monday, 7 February 2022 at 05:05:27 UTC, forkit wrote:
my only concern is the capital U, in @mustUse
This seems a little inconsistent with current attributes??
e.g:
nogc
nothrow
inout
https://dlang.org/spec/attribute.html
also, nodiscard would actually seem more logical, given the
above
On Sunday, 6 February 2022 at 20:45:20 UTC, Ola Fosheim Grøstad
wrote:
On Sunday, 6 February 2022 at 19:14:50 UTC, Paul Backus wrote:
Let me rephrase: I do not understand why you feel the need to
direct these messages at me, personally.
I am sorry if you felt I was addressing you personally. T
On Sunday, 6 February 2022 at 17:07:46 UTC, Ola Fosheim Grøstad
wrote:
On Sunday, 6 February 2022 at 16:20:07 UTC, Paul Backus wrote:
I did not reply (and do not intend to reply) to any of the
numerous other statements you have made in your other replies
to this thread, since they are statement
On Sunday, 6 February 2022 at 16:01:15 UTC, Ola Fosheim Grøstad
wrote:
On Sunday, 6 February 2022 at 15:51:46 UTC, Paul Backus wrote:
If you're still confused *after* you've read the
documentation, feel free to come back and complain to me then.
What I stated has nothing to do with documentati
On Sunday, 6 February 2022 at 15:46:47 UTC, Ola Fosheim Grøstad
wrote:
On Sunday, 6 February 2022 at 15:17:35 UTC, Paul Backus wrote:
On Sunday, 6 February 2022 at 14:44:40 UTC, Ola Fosheim
Grøstad wrote:
It is kinda confusing to call it a user-defined attribute if
it is recognized by the compi
On Sunday, 6 February 2022 at 15:24:17 UTC, Paolo Invernizzi
wrote:
@hold (or @held) ? donwannaopenacanofworms ... my last post
really :-P
Pretend that you are a beginning D programmer, and you come
across one of the following declarations while reading someone
else's code:
@use struct
On Sunday, 6 February 2022 at 14:44:40 UTC, Ola Fosheim Grøstad
wrote:
On Sunday, 6 February 2022 at 13:33:53 UTC, Paul Backus wrote:
@mustUse is a user-defined attribute, and the official style
guide says that names of UDAs should be camelCased:
It is kinda confusing to call it a user-defin
On Sunday, 6 February 2022 at 14:32:31 UTC, Paolo Invernizzi
wrote:
While I like a lot and welcome the addition of this attribute
(so thank you!), I humbly ask to reconsider using the full
lowercase alternative instead of camel case.
Let's conform with the other built-in attributes listed i
On Sunday, 6 February 2022 at 13:40:00 UTC, Paolo Invernizzi
wrote:
On Sunday, 6 February 2022 at 13:33:53 UTC, Paul Backus wrote:
@mustUse is a user-defined attribute, and the official style
guide says that names of UDAs should be camelCased:
https://dlang.org/dstyle.html#naming_udas
...
On Sunday, 6 February 2022 at 10:55:20 UTC, Daniel N wrote:
Guess I'm way too late, I just find it very strange you settled
on mixedCase, it's not used for anything else. (nothrow @nogc).
I also don't agree with the motivation that @use is hard to
search for because @ is an unusual symbol.
On Friday, 28 January 2022 at 13:07:13 UTC, Mike Parker wrote:
Congratulations to Paul Backus. DIP 1038, "@mustUse" has been
accepted after he implemented changes to address concerns from
Walter.
https://github.com/dlang/DIPs/blob/master/DIPs/accepted/DIP1038.md
Update for anyone following t
On Sunday, 23 January 2022 at 14:53:21 UTC, Adam Ruppe wrote:
On Sunday, 23 January 2022 at 14:33:26 UTC, Paul Backus wrote:
Absolutely-no-breakage-ever is basically the C++ approach, and
I have already explained why I think it's a bad idea, though I
recognize that reasonable people can disagre
On Sunday, 23 January 2022 at 12:54:16 UTC, Adam D Ruppe wrote:
I'm not so sure. Isn't the whole point of the versioning thing
so you can use old things that haven't kept up with the latest?
When it was written, sure, they used import std because that's
easy and of course they want the lates
On Sunday, 23 January 2022 at 00:07:17 UTC, forkit wrote:
On Saturday, 22 January 2022 at 05:43:55 UTC, Paul Backus wrote:
(I think it would also be ideal if the namespace `std` were
reserved for the latest stable release...
wouldn't this prevent breaking changes from being allowed in a
new
On Friday, 21 January 2022 at 12:33:25 UTC, Mike Parker wrote:
### Andrei
Andrei brought up std.v2, but this is where memory fails me.
What I do recall is that there was a bit of talk about the
std.v2 namespace and how it will live alongside std, and this
came up because Robert isn't convinced
On Sunday, 16 January 2022 at 00:27:08 UTC, Ali Çehreli wrote:
On 1/15/22 15:49, rikki cattermole wrote:
> If you don't use Matrix, you can ignore this.
I use Emacs. Is that Matrix? :o)
Ali
Actually it looks like there is a Matrix client for emacs:
https://github.com/alphapapa/ement.el
On Wednesday, 12 January 2022 at 20:48:39 UTC, forkit wrote:
Fear of GC is just a catch-all-phrase that serves no real
purpose, and provides no real insight into what programmers are
thinking.
It's all about autonomy and self-government (on the decision of
whether to use GC or not, or when to
On Wednesday, 12 January 2022 at 19:55:41 UTC, Moth wrote:
[snip]
Another issue is the way concatenation is implemented. Since
FixedStrings have compile-time size, this potentially means
every time you concatenate a string in your code you get
another instantiation of FixedString. This can lea
On Tuesday, 11 January 2022 at 17:55:28 UTC, H. S. Teoh wrote:
Generally, I'd advise not conflating your containers with
ranges over your containers: I'd make .opSlice return a
traditional D slice (i.e., const(char)[]) instead of a
FixedString, and just require writing `[]` when you need to
it
On Tuesday, 19 October 2021 at 14:48:20 UTC, Tejas wrote:
On Tuesday, 19 October 2021 at 13:53:04 UTC, Paul Backus wrote:
I this specific case, I agree completely. But there is a
broader pattern in D of projects getting "stuck" because a
specific individual is unable to continue work on them (e
On Tuesday, 19 October 2021 at 13:35:16 UTC, Timon Gehr wrote:
On 11.10.21 03:08, Paul Backus wrote:
Perhaps worth asking why Walter, specifically, is required to
work on @live in order for it to make progress. Is it just
because no one else is willing to step up to the plate, or is
he the o
On Friday, 15 October 2021 at 15:19:26 UTC, Imperatorn wrote:
Btw, why is dmd a memory hog?
Because it doesn't free memory. It just allocates, and relies on
the OS to clean up at process exit.
See https://www.digitalmars.com/articles/b87.html
On Thursday, 14 October 2021 at 13:37:29 UTC, Andrey Zherikov
wrote:
Another thing is that I couldn't use `allMembers` without using
the module name explicitly, because: `__traits(isModule,
__MODULE__)` returns `false` and `__traits(allMembers,
__MODULE__)` gives `"mymodule" can't have members,
On Monday, 11 October 2021 at 00:34:28 UTC, Mike Parker wrote:
On Sunday, 10 October 2021 at 23:36:56 UTC, surlymoor wrote:
Meanwhile @live is in the language, and it's half-baked. Then
there's preview switches that will linger on into perpetuity;
DIPs' implementations that haven't been finis
On Saturday, 9 October 2021 at 23:02:22 UTC, Murilo wrote:
Hi guys, I've just finished the final version of the DMD GUI,
there is Linux and a Windows version, click on the link below
to download it:
https://github.com/MuriloMir/DMD-GUI
Nice. Not something I'd use myself, but it might be helpf
On Friday, 17 September 2021 at 12:39:42 UTC, RazvanN wrote:
Given that points are obtained depending on severity, my
expectation is that reviewers will pay more attention to it
when a PR is submitted. In addition, people that try to score
as much points as possible will be interested in maki
On Thursday, 16 September 2021 at 11:56:21 UTC, Mike Parker wrote:
https://dlang.org/blog/2021/09/16/bugzilla-reward-system/
From the post:
The scoring is designed to reward contributors based on the
importance of the issues they fix, rather than the total number
fixed. As such, issues are a
On Wednesday, 15 September 2021 at 14:48:06 UTC, Tejas wrote:
Assuming I'm correct:
What does it matter whether the parser is a `.c .cpp .d .pl` or
whatever file?
I'm really sorry I'm coming off as abrasive/ungrateful. I have
no intention to belittle the author or the work she has done.
Bu
On Monday, 30 August 2021 at 16:12:57 UTC, Adam D Ruppe wrote:
On Monday, 30 August 2021 at 16:03:29 UTC, Guillaume Piolat
wrote:
Hyped by ProtoObject, this is our hope for a nothrow @nogc
.destroy eventually!
This fails today only because of the rt_finalize hook working
through void*. If you
On Friday, 27 August 2021 at 22:45:15 UTC, WebFreak001 wrote:
I'm just worried about how the memory usage will grow with
this, considering dmd never frees. Maybe I should make it run
as external tool instead of a library so the OS cleans up, but
for that get a performance penalty especially on
`dmdtags` is a tags file generator for D source code that uses
the DMD compiler frontend for accurate parsing.
This release supports 100%-accurate parsing of arbitrary D code
(tested on DMD and Phobos sources), as well as the most
commonly-used command line options, `-R`, `-o`, and `-a`. The
On Wednesday, 25 August 2021 at 13:30:58 UTC, rushsteve1 wrote:
On Wednesday, 25 August 2021 at 06:23:37 UTC, Kagamin wrote:
You marked all functions inline?
If I did then it wasn't on purpose, I was only trying to mark
the handful of helper functions as inline. If you know a
solution to thi
On Tuesday, 24 August 2021 at 02:19:58 UTC, rushsteve1 wrote:
https://github.com/rushsteve1/trash-d
A near drop-in replacement for `rm` that uses the Freedesktop
trash bin. Started because an acquaintance `rm -rf`'d his music
folder and I thought there had to be a better way.
Looks like a ni
On Saturday, 24 April 2021 at 18:16:51 UTC, IGotD- wrote:
One remark I found interesting regarding reference counting.
"In order to properly run the destructor, you have to run the
destructor in an exception handler"
Why do you need to run the destructor in an exception handler?
I assume it
On Sunday, 14 February 2021 at 18:22:14 UTC, superbomba wrote:
I've tried both Chrome and FireFox (I admit they're all old
versions). Interesting that I can visit any stream site like
YT, Twitch, Dailymotion and others normally but unfortunately
not this Jitsi.
The specific browser feature
On Monday, 1 February 2021 at 12:11:46 UTC, Petar Kirov
[ZombineDev] wrote:
On Monday, 1 February 2021 at 11:10:28 UTC, Paul Backus wrote:
Unfortunately, you can't pass more than one command-line
argument on a #! line.
It is possible, using `/usr/bin/env -S command arg1 arg2` , as
of coreutil
On Monday, 1 February 2021 at 09:36:15 UTC, Jacob Carlborg wrote:
On Sunday, 31 January 2021 at 20:36:43 UTC, aberba wrote:
It's finally out!
https://opensource.com/article/21/1/d-scripting
FYI, the code will compile faster if you use `dmd -run` instead
of `rdmd`. If you have multiple files
On Saturday, 30 January 2021 at 16:55:22 UTC, superbomba wrote:
On Saturday, 30 January 2021 at 14:21:48 UTC, Iain Buclaw wrote:
...See you all there!
Can't participate, both browsers gave me:
On FF:
2021-01-30T18:50:28.769Z
[modules/browser/BrowserCapabilities.js] This appears to be
firef
On Tuesday, 26 January 2021 at 16:40:23 UTC, Ola Fosheim Grøstad
wrote:
On Tuesday, 26 January 2021 at 16:05:03 UTC, Paul Backus wrote:
Well, the incorrect behavior is a liability whether we have an
issue for it in bugzilla or not. The issue itself is an asset.
IFF there is development process
On Tuesday, 26 January 2021 at 13:15:05 UTC, Ola Fosheim Grøstad
wrote:
On Monday, 25 January 2021 at 21:25:28 UTC, H. S. Teoh wrote:
So don't look at the bug count as some kind of liability to
rid ourselves of by whatever means possible; rather, look at
it as a sign of life and the opportunity
On Monday, 25 January 2021 at 12:48:48 UTC, Imperatorn wrote:
But, at the same time, I guess it could be a bit demoralizing
you know?
That's true. Sometimes, reality is demoralizing. That doesn't
mean we should hide our heads in the sand and ignore it.
It's kinda obvious when you push it to
On Thursday, 14 January 2021 at 15:30:12 UTC, Dukc wrote:
On Thursday, 14 January 2021 at 15:14:36 UTC, Dukc wrote:
I use Geany, and I'm no power user, I don't know many key
bindings. My way to deal with this is dead stupid: I leave the
character cursor where I am and start scrolling. When I
On Tuesday, 12 January 2021 at 19:49:10 UTC, jmh530 wrote:
I'd rather put the import at the top of the file, or in a
version(unittest) block than that. The problem with those
approaches is that if you have an example unittest, then when a
user tries to run it then they have to put the import in
On Monday, 11 January 2021 at 22:28:04 UTC, jmh530 wrote:
On Monday, 11 January 2021 at 21:33:36 UTC, Paul Backus wrote:
On Monday, 11 January 2021 at 21:17:20 UTC, jmh530 wrote:
Of course, the typical response would be, "well why not use
alias s = static array". I would ask what about an @nogc
On Monday, 11 January 2021 at 21:17:20 UTC, jmh530 wrote:
Of course, the typical response would be, "well why not use
alias s = static array". I would ask what about an @nogc
unittest where the author is trying to limit calls to functions
that aren't really central to what is being tested.
I'
On Tuesday, 22 December 2020 at 16:54:56 UTC, 9il wrote:
On Tuesday, 22 December 2020 at 16:43:30 UTC, ag0aep6g wrote:
On Tuesday, 22 December 2020 at 16:32:20 UTC, 9il wrote:
"Struct non-static methods marked with the return attribute
ensure the returned reference will not outlive the struct
On Tuesday, 22 December 2020 at 03:56:13 UTC, 9il wrote:
On Sunday, 20 December 2020 at 11:00:05 UTC, Tobias Pankrath
wrote:
On Sunday, 15 November 2020 at 04:54:19 UTC, 9il wrote:
Truly algebraic Variant and Nullable with an
order-independent list of types.
Thanks for sharing it!
Could you
On Wednesday, 25 November 2020 at 00:56:39 UTC, sarn wrote:
On Wednesday, 25 November 2020 at 00:20:54 UTC, Paul Backus
wrote:
The exact memory layout and ABI of SumType is deliberately
left unspecified. It's an implementation detail that client
code isn't supposed to rely on. If you want to pa
On Tuesday, 24 November 2020 at 23:02:15 UTC, Dibyendu Majumdar
wrote:
Thanks - I was suggesting adding a description to the
documentation, unless it is already there. Also an ABI
specification would be helpful - what happens when a value is
passed to a C program.
Thanks for the suggestion
On Tuesday, 24 November 2020 at 21:52:47 UTC, Dibyendu Majumdar
wrote:
On Sunday, 15 November 2020 at 20:05:16 UTC, Paul Backus wrote:
SumType is a generic discriminated union type for modern D. It
is designed to
be an improved alternative to `std.variant.Algebraic`.
Nice. Is it possible to
SumType is a generic discriminated union type for modern D. It is
designed to
be an improved alternative to `std.variant.Algebraic`.
Features:
- Pattern matching, including:
- Match-by-introspection ("if it compiles, it matches") (★)
- Multiple dispatch (★)
- Support for self-referen
On Friday, 13 November 2020 at 15:22:03 UTC, Dibyendu Majumdar
wrote:
On Friday, 13 November 2020 at 13:41:50 UTC, Paul Backus wrote:
It sounds like maybe your time would be better spent improving
the official D documentation to say which features and
libraries are compatible with betterC and
On Friday, 13 November 2020 at 12:25:48 UTC, Dibyendu Majumdar
wrote:
Fortunately or not - I have limited time - so I won't be making
changes to D other than very simple patches to switch off some
things. I simply cannot afford to spend time on maintaining a
different code base. My main focus w
On Tuesday, 27 October 2020 at 16:26:10 UTC, vitamin wrote:
Hello,
Older version of sumtype accept this code:
void main(){
import sumtype;
alias Val = SumType!(bool);
const bool b = true;
Val val = b; //fail in newest version
val = b; //fail in newest version
}
but
On Monday, 19 October 2020 at 13:59:42 UTC, Adam D. Ruppe wrote:
On Monday, 19 October 2020 at 13:43:14 UTC, Bastiaan Veelo
wrote:
I'm not suggesting that this fills the need of newbies, but
there is this: https://dlang.org/install.html.
Nobody should ever follow those terrible instructions, t
SumType is a generic sum type for modern D. It is designed to be
an improved
alternative to `std.variant.Algebraic`.
Features:
- Pattern matching, including:
- Match-by-introspection ("if it compiles, it matches") (★)
- Multiple dispatch (★)
- Support for self-referential types (`Thi
On Saturday, 12 September 2020 at 13:40:34 UTC, Per Nordlöw wrote:
On Saturday, 12 September 2020 at 13:03:29 UTC, Paul Backus
wrote:
How many improvements does this warning have to block before
we decide its value for the language is net-negative?
There's also the option of improving the diag
On Saturday, 12 September 2020 at 11:43:03 UTC, MoonlightSentinel
wrote:
Currently looking into enabling it by default but it showed an
interesting side effect. The frontend can now conclude that a
== b is always true if a and b are instances of an empty struct
(without custom opEquals).
Th
On Thursday, 3 September 2020 at 09:24:01 UTC, Jacob Carlborg
wrote:
On Thursday, 3 September 2020 at 08:40:32 UTC, aberba wrote:
The slack I have no ideas how people get in. I know there's a
number of members in there too.
Unfortunately you need to be invited. Anyone can do it, if
you're in
On Thursday, 27 August 2020 at 14:10:36 UTC, Dennis wrote:
On Thursday, 27 August 2020 at 13:32:44 UTC, Paul Backus wrote:
Of course, you could also argue that these are things that
shouldn't be allowed in @safe code to begin with--regardless
of whether pointers are involved.
I did not intend
On Wednesday, 26 August 2020 at 15:34:26 UTC, Dennis wrote:
On Wednesday, 26 August 2020 at 14:29:46 UTC, Dukc wrote:
I think there is a workaround to the variable access being
always safe. Something like this in a dedicated module:
```
struct SystemVar(T, bool safeVal)
{ private T _var;
s
On Sunday, 23 August 2020 at 19:39:35 UTC, Paul Backus wrote:
https://pbackus.github.io/blog/how-does-memory-safety-work-in-d.html
Oops, wrong link. Here's the correct one:
https://pbackus.github.io/blog/what-does-memory-safety-really-mean-in-d.html
https://pbackus.github.io/blog/how-does-memory-safety-work-in-d.html
What exactly do we mean when we talk about "memory safety" in D?
Is it the same thing as "undefined behavior"? Is it ever correct
to mark and `extern(C)` function as `@trusted`? This post is my
attempt to understand, and answ
On Saturday, 25 July 2020 at 18:24:22 UTC, Jesse Phillips wrote:
On Saturday, 25 July 2020 at 14:47:01 UTC, aberba wrote:
On Saturday, 25 July 2020 at 13:28:34 UTC, Adam D. Ruppe wrote:
On Saturday, 25 July 2020 at 11:12:16 UTC, aberba wrote:
Oop! Chaining the writeln too could have increased t
On Thursday, 23 July 2020 at 14:43:23 UTC, Mike Parker wrote:
I've just published the formal announcement of DConf Online
2020 to the blog and shared it on reddit. If you have time,
please check the comments in the reddit thread for any
questions you can answer and myths you can refute about D!
On Thursday, 2 July 2020 at 14:56:09 UTC, aberba wrote:
Why no one is using your D library
So I decided to write a little something special. Its my love
letter to D folks.
https://aberba.vercel.app/2020/why-no-one-is-using-your-d-library/
Excellent article. As the author of a moderately-pop
On Saturday, 27 June 2020 at 15:06:12 UTC, Avrina wrote:
Do you understand what prioritizing is? Fake internet points
are being prioritized over ease of access to the community.
Another way to frame it is that "respecting the rules of another
community (HN) is being prioritized over a minor
On Wednesday, 24 June 2020 at 16:15:30 UTC, Andrei Alexandrescu
wrote:
On 6/23/20 10:31 AM, Meta wrote:
By the way I found this helpful:
https://chrome.google.com/webstore/detail/smile-always/jgpmhnmjbhgkhpbgelalfpplebgfjmbf?hl=en
And for firefox users:
https://addons.mozilla.org/en-US/firef
Are you tired of D's sane, straightforward scoping rules? Itching
for a taste of that old-fashioned C++ madness? Well, itch no
more: addle is here to help.
addle is a tiny library that implements C++-style
argument-dependent lookup (ADL) for D, on an opt-in basis. It
lets you extend existing
On Tuesday, 16 June 2020 at 13:31:49 UTC, Atila Neves wrote:
With a few changes, yes (added missing semicolons, changed
IGeometry to Geometry in `measure`, passed the current module
so tardy can find the UFCS functions, added `@safe pure` to the
UFCS functions:
[...]
void main() {
On Sunday, 14 June 2020 at 16:26:17 UTC, Avrina wrote:
The situation also applies to the only tuple implementation in
D. If you are proposing a new type with emphasis on reducing
the footprint of the tuple then I don't see a problem with
that. Changing the existing tuple implementation would
On Saturday, 13 June 2020 at 15:11:49 UTC, Atila Neves wrote:
https://code.dlang.org/packages/tardy
https://github.com/atilaneves/tardy
Cool stuff!
What's the reasoning behind implementing your own vtables instead
of using D's built-in object system? Don't want to be stuck
inheriting from O
On Saturday, 30 May 2020 at 21:48:32 UTC, Johan wrote:
Great work.
Which compilers (and versions) are available?
-Johan
Looks like dmd [1], ldc [2], and gdc [3] are all there.
[1] https://pkgs.alpinelinux.org/package/edge/community/x86_64/dmd
[2] https://pkgs.alpinelinux.org/package/edge/com
On Saturday, 30 May 2020 at 16:17:49 UTC, Steven Schveighoffer
wrote:
+1 this would be perfect.
Not sure if this would work either, but both of these are
already reserved words:
default @safe:
-Steve
It would probably have to be something more like
`default(@safe)`, since `default @safe:
On Friday, 29 May 2020 at 04:53:07 UTC, Walter Bright wrote:
The subject says it all.
If you care about memory safety, I recommending adding `safe:`
as the first line in all your project modules, and annotate
individual functions otherwise as necessary. For modules with C
declarations, do as
On Thursday, 28 May 2020 at 02:47:01 UTC, Jonathan M Davis wrote:
Walter has acknowledged the problem and seems to think that
because it's the programmer's responsibility to deal with
extern(C) functions correctly (since it's not possible for the
compiler to do it), it's up to the programmer to
On Wednesday, 27 May 2020 at 05:54:32 UTC, Walter Bright wrote:
On 5/26/2020 1:32 PM, Paul Backus wrote:
The reason extern function declarations are particularly
problematic is that changing them from @system-by-default to
@safe-by-default can cause *silent* breakage in existing,
correct code.
On Tuesday, 26 May 2020 at 22:47:03 UTC, Gregory wrote:
If Walter believed greenwashing was actually a problem, then
the best solution to prevent it would be to not make @safe by
default. If it's not that serious of a problem that he will
push through @safe by default, then greenwashing isn't a
1 - 100 of 171 matches
Mail list logo