On Tuesday, 9 September 2025 at 01:08:41 UTC, Brother Bill wrote:
On Tuesday, 9 September 2025 at 00:45:00 UTC, monkyyy wrote:
On Tuesday, 9 September 2025 at 00:40:31 UTC, Brother Bill
wrote:
https://tour.dlang.org/tour/en/gems/opdispatch-opapply
This states: "Any unknown member function call
On Monday, 8 September 2025 at 16:51:09 UTC, Serg Gini wrote:
On Monday, 8 September 2025 at 16:43:10 UTC, Neto wrote:
[...]
It is an old news now.
They decided to use Go, because it was closer to the language
of their initial implementation (TypeScript).
D is expensive for production in mo
On Monday, 8 September 2025 at 21:25:25 UTC, drug007 wrote:
On 08.09.2025 22:55, Neto wrote:
On Monday, 8 September 2025 at 16:51:09 UTC, Serg Gini wrote:
And not sure if ecosystem was a significant weight in the
decision.
Why isn't D production ready?
I've been trying to figure it out fo
On Monday, 8 September 2025 at 16:23:23 UTC, Brother Bill wrote:
On Monday, 8 September 2025 at 14:42:01 UTC, evilrat wrote:
probably because you have declared nested function `add`
inside `main`, this creates a delegate closure capturing
`main` scope, if you don't want that just mark `add` s
On 9/8/25 9:51 AM, Serg Gini wrote:
> So I don't think they were considering D at all. Most probably they had
> some short-list of the language that their team knows and that are
> suitable for the task.
In my experience, such project "decisions" are rationalizations after
the fact. Like in mos
On Monday, 8 September 2025 at 19:55:20 UTC, Neto wrote:
Why isn't D production ready?
For this type of questions is kinda hard to prepare a short
answer..
So instead of direct answer consider to check this equation:
Being production ready is a hard/complicated target..
large language = co
On Monday, 8 September 2025 at 16:43:10 UTC, Neto wrote:
this is the reasoning
https://github.com/microsoft/typescript-go/discussions/411
I wonder if they did consider D language. First comment says
why Rust would be a good choice "If not C#, I would have
expected Rust, since that's where the
On Monday, 8 September 2025 at 16:43:10 UTC, Neto wrote:
this is the reasoning
https://github.com/microsoft/typescript-go/discussions/411
I wonder if they did consider D language. First comment says
why Rust would be a good choice "If not C#, I would have
expected Rust, since that's where the
On Monday, 8 September 2025 at 14:42:01 UTC, evilrat wrote:
probably because you have declared nested function `add` inside
`main`, this creates a delegate closure capturing `main` scope,
if you don't want that just mark `add` static.
Yep, as a nested function, this is a delegate, not a func
this is the reasoning
https://github.com/microsoft/typescript-go/discussions/411
I wonder if they did consider D language. First comment says why
Rust would be a good choice "If not C#, I would have expected
Rust, since that's where the rest of the ecosystem is. So,
another surprise there." i
It works by making doSomething as a delegate.
On Monday, 8 September 2025 at 14:42:01 UTC, evilrat wrote:
probably because you have declared nested function `add` inside
`main`, this creates a delegate closure capturing `main` scope,
if you don't want that just mark `add` static.
Marking add static works.
Still don't understand why thi
https://tour.dlang.org/tour/en/basics/delegates
This is so simple. What is D complaining about?
Should this also work with a Template, as shown?
```
import std.stdio;
void main()
{
// auto add(T)(T lhs, T rhs)
// {
// return lhs + rhs;
// }
int add
13 matches
Mail list logo
