On Tue, Mar 22, 2022 at 7:21 PM Larry Garfield
wrote:
> Are we talking about *arbitrary* user-space operator overloading?
> Because a very specific, non-arbitrary, well-designed operator
> overloading RFC was just rejected.
>
Yup. This was pointed out to me in r11, I guess I must have missed that
On Tue, Mar 22, 2022, at 12:59 PM, Sara Golemon wrote:
> On Tue, Mar 22, 2022 at 10:31 AM Christian Schneider
> wrote:
>
>> Am 22.03.2022 um 16:14 schrieb Sara Golemon :
>> > So while I said I wanted to avoid the firestorm suggesting userspace
>> > overloading would bring, maybe that's the questio
On Tue, Mar 22, 2022 at 10:28 AM Pierre wrote:
> Le 22/03/2022 à 16:14, Sara Golemon a écrit :
> > Who's just a hard-nope on userspace operator overloading? If your
> reasons
> > go beyond foot-gun (and that is a valid reason), could you share what
> those
> > reasons are?
> >
>
> I am a not so
On Tue, Mar 22, 2022 at 10:31 AM Christian Schneider
wrote:
> Am 22.03.2022 um 16:14 schrieb Sara Golemon :
> > So while I said I wanted to avoid the firestorm suggesting userspace
> > overloading would bring, maybe that's the question to ask:
> >
> > Who's just a hard-nope on userspace operator
>
> I'd build this in userspace, but of course we don't have operator
> overloading, so the API would be a somewhat uglier function call:
It is currently possible to get operator overloads in userspace using FFI
(using my fork of lisachenko's z-engine to FFI into PHP calls). I made a
quick proto
Am 22.03.2022 um 16:14 schrieb Sara Golemon :
> So while I said I wanted to avoid the firestorm suggesting userspace
> overloading would bring, maybe that's the question to ask:
>
> Who's just a hard-nope on userspace operator overloading? If your reasons
> go beyond foot-gun (and that is a valid
Le 22/03/2022 à 16:14, Sara Golemon a écrit :
On Tue, Mar 22, 2022 at 5:38 AM Robert Landers
wrote:
But why can't we have generic operator overloading in which case this could
be completely built by libraries in userland?
I mean... honestly, I feel like I come back around to this very quickl
On Tue, Mar 22, 2022 at 5:38 AM Robert Landers
wrote:
>
> But why can't we have generic operator overloading in which case this could
> be completely built by libraries in userland?
>
I mean... honestly, I feel like I come back around to this very quickly.
Generic overloading gives us much more
On Tue, Mar 22, 2022 at 10:41 AM Michał Marcin Brzuchalski <
michal.brzuchal...@gmail.com> wrote:
> I don't have much to say on that besides that I feel it's a great idea
> and if that can be built with parametrized type streams (not limited to
> strings only)
> then I'd be even more thrilled with
I don't have much to say on that besides that I feel it's a great idea
and if that can be built with parametrized type streams (not limited to
strings only)
then I'd be even more thrilled with such functionality.
Thanks for this idea and I hope it get materialized soon.
Cheers,
Michał Marcin Brzu
On Mon, Mar 21, 2022, at 10:23 AM, Sara Golemon wrote:
> TL;DR - Yeah, PHP, but what if C++? Feel free to tell me I'm wrong and
> should feel bad. THIS IS ONLY IDLE MUSINGS.
>
> I was reading the arbitrary string interpolation thread (which I have mixed
> feelings on, but am generally okay with),
11 matches
Mail list logo
