Mike Parker kirjoitti 14.5.2024 klo 16.23:
The D Language Foundation's monthly meeting for January 2024 was held on
Friday the 12th. There were two things of particular note about this
meeting.
Thanks for the write-up once again! Always nice to know what is cooking,
even when the news come
Wow I see I was mentioned at a lot at this meeting!
In saying that I do have some points to add about Item 2 data structures.
Data structures come in one of two forms generally: owning and non-owning.
### Non-owning
Non-owning is the simplest, its an index.
It doesn't own any memory that
On Tuesday, 14 May 2024 at 14:01:28 UTC, Hipreme wrote:
[snip]
### Item 8
There was a project which is basically rdmd but faster out
there, done by Jonathan Marler.
- https://github.com/dragon-lang/rund
Sometime ago I thought about just pushing to d tools, but since
no one cared about, I
On Tuesday, 14 May 2024 at 13:23:17 UTC, Mike Parker wrote:
The D Language Foundation's monthly meeting for January 2024
was held on Friday the 12th. There were two things of
particular note about this meeting.
[...]
I have some things to feedback on those points
### Item 6
I had done my
The D Language Foundation's monthly meeting for January 2024 was
held on Friday the 12th. There were two things of particular note
about this meeting.
First, Jonathan Davis joined us for the first time and is now a
permanent member. We're very happy to have him aboard.
Second, this was the
On Saturday, 29 July 2023 at 14:37:32 UTC, Mike Parker wrote:
I mistakenly posted the summary in the General forum. You can
find it here:
https://forum.dlang.org/thread/jzlympfqmwckaiuhq...@forum.dlang.org [geometry
dash world](https://geometrydashworld.net)
Good, I'm looking forward to
On Wednesday, 3 April 2024 at 16:25:49 UTC, Mike Parker wrote:
The D Language Foundation's quarterly meeting for January, 2024
took place on Friday the 5th at 15:00 UTC. It lasted for about
45 minutes.
One update is that by now, Luna is now maintaining with me the
Objective-C meta library
On Wednesday, 3 April 2024 at 16:25:49 UTC, Mike Parker wrote:
The D Language Foundation's quarterly meeting for January, 2024
took place on Friday the 5th at 15:00 UTC. It lasted for about
45 minutes.
[snip]
Thanks for the write-up, as always.
__Question about Ddoc__
Second, when
The D Language Foundation's quarterly meeting for January, 2024
took place on Friday the 5th at 15:00 UTC. It lasted for about 45
minutes.
Our quarterly meetings are where representatives from businesses
big and small can come to bring us their most pressing D issues,
status reports on their
On Wednesday, 27 March 2024 at 20:32:16 UTC, Mike Parker wrote:
[...]
Thank you for summarising these!
The D Language Foundation's monthly meeting for December 2023
took place on Friday the 8th at 16:00 UTC. It lasted two hours.
## The Attendees
The following people attended the meeting:
* Andrei Alexandrescu
* Paul Backus
* Walter Bright
* Iain Buclaw
* Martin Kinkelin
* Razvan Nitu
* Mike
On Monday, 4 March 2024 at 11:07:07 UTC, Mike Parker wrote:
### Steve and Me
I have to apologize to Steve. I managed to botch the initial
recording, so whatever he and I said at the top of the meeting
is lost. I'm pretty sure I talked about preliminary planning
for DConf '24, but beyond
On Monday, 4 March 2024 at 11:19:57 UTC, Mike Parker wrote:
On Monday, 4 March 2024 at 11:17:16 UTC, Sergey wrote:
On Monday, 4 March 2024 at 11:07:07 UTC, Mike Parker wrote:
snip
Thanks for keep posting it
just a bit awkward to read in March about November..
Yeah, sorry about that. I'll
## October
We had no regular planning sessions in October. Instead, there
were two workgroup meetings focused on DMD as a library. These
took place after the monthly meeting and involved several people
who were stakeholders, were interested in the project, or had
some level of experience with
On Monday, 4 March 2024 at 11:17:16 UTC, Sergey wrote:
On Monday, 4 March 2024 at 11:07:07 UTC, Mike Parker wrote:
snip
Thanks for keep posting it
just a bit awkward to read in March about November..
Yeah, sorry about that. I'll get caught up this month. Then I'll
be back to posting them
On Monday, 4 March 2024 at 11:07:07 UTC, Mike Parker wrote:
snip
Thanks for keep posting it
just a bit awkward to read in March about November..
# Summary
The D Language Foundation's monthly meeting for November 2023
took place on Friday, the 10th, at 16:00 UTC. It lasted around
one hour and ten minutes.
## The Attendees
The following people attended the meeting:
* Walter Bright
* Martin Kinkelin
* Mathias Lang
* Átila Neves
* Mike
On Sunday, 31 December 2023 at 11:12:23 UTC, Mike Parker wrote:
The D Language Foundation's monthly meeting for October 2023
took place on Friday the 13th at 15:00 UTC. It lasted around
one hour and thirty minutes. I was unable to attend, so thanks
to Razvan for running it and to Dennis for
On Monday, 1 January 2024 at 10:50:22 UTC, Konstantin wrote:
On Sunday, 31 December 2023 at 11:12:23 UTC, Mike Parker wrote:
Finally, he brought up code-d, [the Visual Studio Code
extension for D](https://github.com/Pure-D/code-d) maintained
by Jan Jurzitza (Webfreak). Steve said that it was
On Sunday, 31 December 2023 at 11:12:23 UTC, Mike Parker wrote:
Finally, he brought up code-d, [the Visual Studio Code
extension for D](https://github.com/Pure-D/code-d) maintained
by Jan Jurzitza (Webfreak). Steve said that it was great when
it worked, but there were a lot of weird things
On Sunday, 31 December 2023 at 11:12:23 UTC, Mike Parker wrote:
(__UPDATE__: Both [the Bugzilla
issue](https://issues.dlang.org/show_bug.cgi?id=24153) and [the
pull request](https://github.com/dlang/dmd/pull/15627) have
since been closed, as the issue is no longer reproducible.)
I just
On Sunday, 31 December 2023 at 11:12:23 UTC, Mike Parker wrote:
The D Language Foundation's monthly meeting for October 2023
took place on Friday the 13th at 15:00 UTC. It lasted around
one hour and thirty minutes.
[chinese
version](https://fqbqrr.blog.csdn.net/article/details/135319694)
On 01/01/2024 12:12 AM, Mike Parker wrote:
Next, he said he'd discovered that a one-line file with |import
std.file| takes 200ms to compile, and that was nuts. He needed to figure
out at some point exactly what the problem was. It was just semantic
analysis just from the import. He wasn't even
The D Language Foundation's monthly meeting for October 2023 took
place on Friday the 13th at 15:00 UTC. It lasted around one hour
and thirty minutes. I was unable to attend, so thanks to Razvan
for running it and to Dennis for recording it.
Two attendees were first-timers: Adam Wilson and
On Wednesday, 6 December 2023 at 16:28:08 UTC, Mike Parker wrote:
## The Next Meetings
We had our October monthly meeting one week after this meeting.
The next quarterly should happen on January 5, 2024. We had no
regular planning sessions in October, but two workgroup
meetings took place
On Monday, 11 December 2023 at 19:55:38 UTC, Timon Gehr wrote:
There is the following trick. Not ideal since the length cannot
be inferred, but this successfully injects alloca into the
caller's scope.
Wow, what a great hack - I'd have never came up with that!
On Monday, 11 December 2023 at 19:55:38 UTC, Timon Gehr wrote:
... this successfully injects alloca into the caller's scope.
```d
import core.stdc.stdlib:alloca;
import std.range:ElementType;
import core.lifetime:moveEmplace;
struct VLA(T,alias len){
T[] storage;
this(R)(R
On Monday, 11 December 2023 at 08:24:55 UTC, Bastiaan Veelo wrote:
On Sunday, 10 December 2023 at 22:59:06 UTC, Nicholas Wilson
wrote:
Or you could use grep with `--output-ll` as noted by Johan
https://github.com/ldc-developers/ldc/issues/4265#issuecomment-1376424944 although this will be with
On Monday, 11 December 2023 at 22:04:34 UTC, Nicholas Wilson
wrote:
And please do get in touch with Bruce Carneal if you want some
tips and insight with the practical and applied side of
dcompute (also with auto-vectorisation) as he has used it a lot
more than I have.
dcompute needs some
On Monday, 11 December 2023 at 08:24:55 UTC, Bastiaan Veelo wrote:
On Sunday, 10 December 2023 at 22:59:06 UTC, Nicholas Wilson
wrote:
Always happy to help if you're interested in looking into
using dcompute.
Thank you, I'll let you know!
And please do get in touch with Bruce Carneal if you
On 12/11/23 20:55, Timon Gehr wrote:
There is the following trick. Not ideal since the length cannot be
inferred, but this successfully injects alloca into the caller's scope.
I see Nick already brought it up.
On 12/6/23 17:28, Mike Parker wrote:
One way to do that in D is to use `alloca`, but that's an issue because
the memory it allocates has to be used in the same function that calls
the `alloca`. So you can't, e.g., use `alloca` to alloc memory in a
constructor, and that prevents using it in
On Sunday, 10 December 2023 at 15:08:05 UTC, Bastiaan Veelo wrote:
We are looking forward to being able to safely use LDC, because
tests show that it has the potential to at least double the
performance.
Yes, and that's before you its excellent SIMD capabilities :)
On Sunday, 10 December 2023 at 22:59:06 UTC, Nicholas Wilson
wrote:
Always happy to help if you're interested in looking into using
dcompute.
Thank you, I'll let you know!
Or you could use grep with `--output-ll` as noted by Johan
On Sunday, 10 December 2023 at 18:16:05 UTC, Nick Treleaven wrote:
You can call `alloca` as a default argument to a function. The
memory will be allocated on the caller's stack before calling
the function:
https://github.com/ntrel/stuff/blob/master/util.d#L113C1-L131C2
I've just tested and it
On Sunday, 10 December 2023 at 16:08:45 UTC, Bastiaan Veelo wrote:
On Sunday, 10 December 2023 at 15:31:55 UTC, Richard (Rikki)
Andrew Cattermole wrote:
It will be interesting to hear how dcompute will fare in your
situation, due to it being D code it should be an incremental
improvement
On Wednesday, 6 December 2023 at 16:28:08 UTC, Mike Parker wrote:
One way to do that in D is to use `alloca`, but that's an issue
because the memory it allocates has to be used in the same
function that calls the `alloca`. So you can't, e.g., use
`alloca` to alloc memory in a constructor, and
On Sunday, 10 December 2023 at 17:11:04 UTC, Siarhei Siamashka
wrote:
On Sunday, 10 December 2023 at 15:08:05 UTC, Bastiaan Veelo
wrote:
The compiler can check if `scope` delegates escape a function,
but it only does this in `@safe` code --- and our code is long
from being `@safe`. So it was a
On Sunday, 10 December 2023 at 15:08:05 UTC, Bastiaan Veelo wrote:
1) Missing `scope` storage class specifiers on `delegate`
function arguments. This can be chalked down as a beginner
error, but also one that is easy to miss. If you didn't know:
without `scope` the compiler cannot be sure that
On Sunday, 10 December 2023 at 15:31:55 UTC, Richard (Rikki)
Andrew Cattermole wrote:
It will be interesting to hear how dcompute will fare in your
situation, due to it being D code it should be an incremental
improvement once you're ready to move to D fully.
Yes, dcompute could mean
That is awesome to hear!
If the move towards ldc has the potential to half your run time, that is
quite a significant improvement for your customers.
It will be interesting to hear how dcompute will fare in your situation,
due to it being D code it should be an incremental improvement once
On Wednesday, 6 December 2023 at 16:28:08 UTC, Mike Parker wrote:
Bastiaan reported that SARC had been testing their D codebase
(transpiled from Pascal---[see Bastiaan's DConf 2019
talk](https://youtu.be/HvunD0ZJqiA)). They'd found the
multithreaded performance worse than the Pascal version.
On Wednesday, 6 December 2023 at 16:28:08 UTC, Mike Parker wrote:
### Bastiaan
They'd found the multithreaded performance worse than the
Pascal version. He said that execution time increased with more
threads and that it didn't matter how many threads you throw at
it. It's the latter problem
This needs to be taken out of DRuntime because DRuntime is
distributed pre-compiled, and that ties it to a specific
compiler API, which isn't good. Instead, we should distribute
it as a package. It's something he'd brought up before.
Why not directly distribute DRuntime as a source? or
The D Language Foundation's quarterly meeting for October 2023
took place on Friday the 6th at 15:00 UTC. This was quite a short
one as far as quarterlies go, clocking in at around 35 minutes.
## The Attendees
The following people attended the meeting:
* Mathis Beer (Funkwerk)
* Walter
On Saturday, 2 September 2023 at 20:27:04 UTC, Bonarc wrote:
On Wednesday, 30 August 2023 at 14:19:03 UTC, FeepingCreature
wrote:
When you want to react to ~every keypress in a language server
impl with updated coloring, it starts to be problematic. Think
in terms of "UI feedback" rather than
On Wednesday, 30 August 2023 at 14:19:03 UTC, FeepingCreature
wrote:
When you want to react to ~every keypress in a language server
impl with updated coloring, it starts to be problematic. Think
in terms of "UI feedback" rather than "project compilation".
You only need an AST for this though
On Wednesday, 30 August 2023 at 14:19:03 UTC, FeepingCreature
wrote:
On Friday, 25 August 2023 at 02:10:25 UTC, harakim wrote:
I'm also curious why a 500ms compile time would be generally
recognized as way too long. Is it because it has potential to
be faster or does it cause some legitimate
On Friday, 25 August 2023 at 02:10:25 UTC, harakim wrote:
I'm also curious why a 500ms compile time would be generally
recognized as way too long. Is it because it has potential to
be faster or does it cause some legitimate problem? That's a
question at large, not for Matheus.
When you want
On Friday, 25 August 2023 at 01:20:28 UTC, matheus wrote:
Reading over about other languages CT problems I wonder how
this half second is too terrible. =]
I barely see any difference between 500ms to 1000ms.
I love the fast compile time of D. It feels so freeing.
Contrast that to a Visual
On Tuesday, 22 August 2023 at 12:59:12 UTC, Mike Parker wrote:
...
Adam said his library compiled in half a second. Robert said
that was still too slow. His work project didn't compile in
half a second. He said his goal was that by the time of the
key-up event after pressing 'Enter' on Ninja
On Tuesday, 22 August 2023 at 21:36:49 UTC, An Pham wrote:
1. DMD does not have consistent way of defining system
attribute which can cause conflict with user attribute (DMD
system attribute should start with underscore character, "_")
Not true, these attributes follow module namespacing
### Dennis
Dennis said he'd been working on that AA PR, but had nothing
else to report. He still had some other things to pursue, like
looking at pattern support for the deprecation (-d/-de/-dw) and
obsolete warning (-wo) switches, as well as the `standalone`
attribute or pragma for static
On Tuesday, 22 August 2023 at 12:59:12 UTC, Mike Parker wrote:
### Robert
Robert said he was happy. Dennis asked if the compiler was fast
enough (as regular readers of these summaries may know, Robert
often says the compiler is too slow). Robert said it's still
slow. He just wanted to see
The D Language Foundation's monthly meeting for August 2023 took
place on the 11th. At just under 35 minutes, it was our shortest
monthly meeting to date.
## The attendees
The following people attended the meeting:
* Walter Bright
* Ali Çehreli
* Martin Kinkelin
* Dennis Korpel
* Mathias Lang
On Friday, 11 August 2023 at 13:37:57 UTC, Mike Parker wrote:
The D Language Foundation's monthly meeting for July 2023 took
place on the 14th.
[...]
The idea was that once a library works in D and is debugged, it
will stay working in D unless it's something we can't live with
in older code.
On Friday, 11 August 2023 at 13:37:57 UTC, Mike Parker wrote:
__void initialing Booleans__
Dennis wasn't yet finished. The last item he had for us was [a
PR he had submitted](https://github.com/dlang/dmd/pull/15362)
that marks as `@system` the void initialization of a `bool`, or
anything
Addressing deprecations, I think deprecation messages are good if
we are writing code that will break things. I would be surprised
if anyone wanted these off by default for *new* code they write.
I can see a case for suppressing new deprecations in existing
code so you don't lose the
On Friday, 11 August 2023 at 13:37:57 UTC, Mike Parker wrote:
### Walter
Walter said we had already covered most of what he'd wanted to
talk about. Aside from that, he was focused on bug fixes, going
through the deprecation list, and looking into [adding support
for the ENDBR
On Monday, 14 August 2023 at 12:20:50 UTC, Dom DiSc wrote:
On Monday, 14 August 2023 at 08:42:17 UTC, claptrap wrote:
Maybe if the compiler detects that deprecated features are
being used it could add a line to the output...
"To check for usage of deprecated features use the '-wo'
switch"
On Monday, 14 August 2023 at 08:42:17 UTC, claptrap wrote:
A simple 1 line "friendly reminder" instead of pages of
warnings, surely people could live with that?
Well, given that D compiler is also a unittesting tool, codecov
analyzer, documentation generator, profiler, static analyzer,
build
On Monday, 14 August 2023 at 08:42:17 UTC, claptrap wrote:
Maybe if the compiler detects that deprecated features are
being used it could add a line to the output...
"To check for usage of deprecated features use the '-wo' switch"
A simple 1 line "friendly reminder" instead of pages of
On Friday, 11 August 2023 at 13:37:57 UTC, Mike Parker wrote:
The D Language Foundation's monthly meeting for July 2023 took
### Nick
Nick had nothing new for us but did have some comments on the
`-wo` switch. He thought it was great. However, since there's
no indication by default if code is
The D Language Foundation's monthly meeting for July 2023 took
place on the 14th. It lasted roughly one hour and forty-five
minutes. John Colvin, who has participated in several quarterlies
representing Symmetry, joined us for the first time as a
permanent member of the monthlies.
## The
We had two planning sessions in July, one on the 21st and one on
the 28th.
## Language Editions
### Background
I first reported on our new deprecation policy in [my June
Planning
Update](https://forum.dlang.org/post/jmtcppvsweimsojla...@forum.dlang.org). Later, Walter expanded on that in a
I mistakenly posted the summary in the General forum. You can
find it here:
https://forum.dlang.org/thread/jzlympfqmwckaiuhq...@forum.dlang.org
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
On Thursday, 13 July 2023 at 14:00:49 UTC, Mike Parker wrote:
said in the chat window that this is a straight-up bug). Átila
had also learned that static constructors should always be
`nothrow`. Walter said he couldn't see why anyone would write a
static constructor that throws. Átila said
The monthly meeting for June 2023 took place on Friday the 2nd at
15:00 UTC. It lasted about an hour. We had three new faces for
this one: Adam D. Ruppe, Steven Schveighoffer, and Nick
Treleaven. I'll be sending them invites to all of our future
monthlies, but we've left it up to them to
On Tuesday, 27 June 2023 at 14:18:52 UTC, Mike Parker wrote:
I still will put at least three or four weeks between the
meetings and the summaries.
I appreciate your summary here. This was very insightful!
On Tuesday, 27 June 2023 at 12:36:20 UTC, Sergey wrote:
After that real person could verify result and make small
corrections. It should significantly reduce effort and decrease
time-to-market :)
Yes. The next version of Davinci Resolve (which I use for video
editing) will have automated
On Friday, 23 June 2023 at 14:32:51 UTC, Mike Parker wrote:
The monthly meeting for May 2023 took place on Friday the 5th
at 14:00 UTC. It lasted about an hour and a half.
Hi Mike.
Does anyone consider some automatization and application of
modern technologies for the process of meeting
If you feel up to doing a practice talk, you're welcome to join us on
BeerConf!
On Friday, 23 June 2023 at 14:32:51 UTC, Mike Parker wrote:
[...]
Walter brought up [Sebastiaan Koppe's presentation from last
year](https://youtu.be/hJhNhIeq29U) on structured concurrency.
He said he'd like to see Sebastiaan there this year for an
update on the project, preferably as a
On Friday, 23 June 2023 at 14:32:51 UTC, Mike Parker wrote:
The monthly meeting for May 2023 took place on Friday the 5th
at 14:00 UTC. It lasted about an hour and a half. This was the
last meeting before we started our new planning sessions.
Nice to read on what you guys are doing!
—
Dmitry
The monthly meeting for May 2023 took place on Friday the 5th at
14:00 UTC. It lasted about an hour and a half. This was the last
meeting before we started our new planning sessions.
The following people attended:
* Walter Bright
* Iain Buclaw
* Ali Çehreli
* Martin Kinkelin
* Dennis Korpel
*
On Monday, 15 May 2023 at 18:15:54 UTC, jmh530 wrote:
On Monday, 15 May 2023 at 18:02:49 UTC, ryuukk_ wrote:
[snip]
It can be frustrating when you are are neck deep in some
complicated problem to explain to people who haven't spent the
same amount of time with it as you have.
That poster
On Monday, 15 May 2023 at 18:02:49 UTC, ryuukk_ wrote:
[snip]
It can be frustrating when you are are neck deep in some
complicated problem to explain to people who haven't spent the
same amount of time with it as you have.
On Monday, 15 May 2023 at 17:44:20 UTC, Dany12L wrote:
On Monday, 15 May 2023 at 14:26:52 UTC, ryuukk_ wrote:
On Sunday, 14 May 2023 at 21:47:51 UTC, Dany12L wrote:
On Sunday, 14 May 2023 at 18:59:52 UTC, ryuukk_ wrote:
I'll end up just sticking to C if nobody understand
Fine but what do
On Monday, 15 May 2023 at 14:26:52 UTC, ryuukk_ wrote:
On Sunday, 14 May 2023 at 21:47:51 UTC, Dany12L wrote:
On Sunday, 14 May 2023 at 18:59:52 UTC, ryuukk_ wrote:
I'll end up just sticking to C if nobody understand
Fine but what do you solve? If you need memcpy you will in any
case have
On Sunday, 14 May 2023 at 21:47:51 UTC, Dany12L wrote:
On Sunday, 14 May 2023 at 18:59:52 UTC, ryuukk_ wrote:
I'll end up just sticking to C if nobody understand
Fine but what do you solve? If you need memcpy you will in any
case have to implement it yourself or use some already made
On Sunday, 14 May 2023 at 23:53:41 UTC, max haughton wrote:
On Sunday, 14 May 2023 at 12:47:59 UTC, Mike Parker wrote:
[...]
Some thoughts on testing:
1. This (MacOS) failure has been fixed (by me). It apparently
also occurred with some other LibCs out there prior to that
too. In future
On 15/05/2023 11:53 AM, max haughton wrote:
2. At a bigger scale: We probably have too many CI pipelines. The main
ones that I have
in mind that really could go are the OMF pipelines --- In OMF we have
some ancient baggage which we don't need and shouldn't want to support
anymore: [Microsoft
On Sunday, 14 May 2023 at 12:47:59 UTC, Mike Parker wrote:
__CI failures__
Dennis started by saying that the CI was randomly failing
again. He didn't have a Mac, so he'd been unable to chase down
the problem. Random CI failures are a recurring problem. There
are so many checks, and he
On Sunday, 14 May 2023 at 18:59:52 UTC, ryuukk_ wrote:
I'll end up just sticking to C if nobody understand
Fine but what do you solve? If you need memcpy you will in any
case have to implement it yourself or use some already made
library.
The same thing happens on D.
On Sunday, 14 May 2023 at 19:38:38 UTC, ryuukk_ wrote:
Now you suggest me to depend on WASI by default
Unbelievable
It's getting hard to maintain composure
Then I'll leave it here. There's apparently a big problem with
the solutions I provided that I'm supposed to know, but I don't,
and
On Sunday, 14 May 2023 at 19:13:50 UTC, Dennis wrote:
On Sunday, 14 May 2023 at 18:59:52 UTC, ryuukk_ wrote:
WASI is not WASM, please don't suggest that as a solution,
it's not, this is frustrating to read what you suggest when i
bring to you problems
I've literally had the same problem as
On Sunday, 14 May 2023 at 18:59:52 UTC, ryuukk_ wrote:
WASI is not WASM, please don't suggest that as a solution, it's
not, this is frustrating to read what you suggest when i bring
to you problems
I've literally had the same problem as you (missing references to
libc symbols when targeting
On Sunday, 14 May 2023 at 18:51:38 UTC, Dennis wrote:
Then my project no longer compile, thanks a lot!
When you use a custom druntime, you can't expect stability when
you upgrade the compiler but not your druntime. The real issue
here is that there is no proper support for WebAssembly in
On Sunday, 14 May 2023 at 18:51:38 UTC, Dennis wrote:
On Sunday, 14 May 2023 at 16:02:00 UTC, ryuukk_ wrote:
I wanted to target WASM, if your hooks call into libC, i can't
target WASM..
Good news, there's implementations of libc for WASM
WASI is not WASM, please don't suggest that as a
On Sunday, 14 May 2023 at 16:02:00 UTC, ryuukk_ wrote:
I wanted to target WASM, if your hooks call into libC, i can't
target WASM..
Good news, there's implementations of libc for WASM (example:
https://archlinux.org/packages/community/any/wasi-libc/), and
linking them doesn't even increase
Razvan next brought up Teodor Dutu's work on converting
DRuntime hooks to templates. An intended side effect of this
effort is that it should make things more usable in BetterC,
but sometimes, getting real work done in one of these templates
means calling into the C library (memset, memcpy,
On 15/05/2023 12:47 AM, Mike Parker wrote:
Átila said he'd been thinking about copying Herb Sutter's idea for
zero-overhead C++ exceptions. He said the basic idea is that you get rid
of exceptions while keeping the syntax. (Here's a link to the PDF
We held the monthly meeting for April 2023, on Friday the 14th at
14:00 UTC. It lasted just short of an hour and a half. We'd [had
a quarterly meeting the previous
week](https://forum.dlang.org/thread/yuewobigwhvrtfxlz...@forum.dlang.org). This was the first time wev'e held a monthly meeting in
On Friday, 28 April 2023 at 19:50:55 UTC, max haughton wrote:
1. The conversation about formatters is not quite on the money
wrt internals, sdfmt doesn't work as written. I will write
something explaining the two both architecturally (politically
really for the purposes of this debate) and
On Friday, 28 April 2023 at 14:29:47 UTC, Mike Parker wrote:
The D Language Foundation's second quarterly meeting for 2023
took place on April 7 at 14:00 UTC. It lasted just over an
hour. This was the first "standalone" quarterly meeting, where
the foundation's monthly discussion was split
On Friday, 28 April 2023 at 16:25:03 UTC, Steven Schveighoffer
wrote:
On 4/28/23 11:42 AM, jmh530 wrote:
2) It would be cool to have a built-in way to profile
unittests by module. So for instance, the output would be how
long it took the unit tests to run, broken out by module and
then with a
On 4/28/23 11:42 AM, jmh530 wrote:
2) It would be cool to have a built-in way to profile unittests by
module. So for instance, the output would be how long it took the unit
tests to run, broken out by module and then with a total.
This is a runtime thing. You can customize it:
On Friday, 28 April 2023 at 14:29:47 UTC, Mike Parker wrote:
The D Language Foundation's second quarterly meeting for 2023
took place on April 7 at 14:00 UTC. It lasted just over an
hour. This was the first "standalone" quarterly meeting, where
the foundation's monthly discussion was split
The D Language Foundation's second quarterly meeting for 2023
took place on April 7 at 14:00 UTC. It lasted just over an hour.
This was the first "standalone" quarterly meeting, where the
foundation's monthly discussion was split into a separate meeting
the following week.
Two new members
1 - 100 of 523 matches
Mail list logo
