Proposal: Database Engine for D

Andrei Alexandrescu via Digitalmars-d digitalmars-d at
Sun Jan 3 16:50:20 PST 2016

On 1/2/16 7:23 AM, Jacob Carlborg wrote:
> On 2016-01-01 11:45, Ola Fosheim Grøstad wrote:
>> In D1 Walter made a point about restricting operator overloading to
>> discourage reuse of operators. In D2 there are many ways to create your
>> own weird syntax, but Walter is locked on his D1 position, even though
>> it makes little sense in D2.
>> This is an overarching theme in D: the design rationale, that goes a
>> decade back and is based on making a restricted easy to use version of
>> C++, does not change, even though the context is very different in 2015
>> and the premises has changed.
>> These things are unlikely to change without a fork. Which is a pitty as
>> D needs a more coherent design to get out of stagnation.
> The core developers are making a big deal out of being able to have
> DSL's as string literals and process them at compile time. Although
> that's kind of pointless with SQL, since one still needs to send to
> string to the database to perform the query. The only thing that's
> possible is to validate the syntax at compile time.

Binding D variables to SQL expressions also comes to mind. -- Andrei

More information about the Digitalmars-d mailing list