* Darren Duncan <darren@darrenduncan.net> [2023-08-22 19:44:50 -0700]: > On 2023-08-22 11:43 a.m., Oodler 577 via perl5-porters wrote: > > ... your DbC efforts > > (which btw do not conflict with Perl::Types, a point we've made). > > Perhaps you can show where Perl::Types, as we've demonstrated would > > conflict with Oshun. I am not suggesting they are directly composable, > > but Perl::Types could definitely assist you where otherwise you'd > > just be using regular expressions everywhere (behind some sugar, > > of course). > > That last thing you said about "otherwise you'd just be using regular > expressions everywhere" seems like an unfounded assumption to me. > > While Perl::Types could serve as a foundation for Oshun, there's also no > reason at all that an Oshun implementation couldn't be written against Perl > directly AND Oshun would use exactly the same methods Perl::Types would to > access the "real" Perl type system directly and NOT using regular > expressions. > > It is true that some other type implementations in Perl use regular > expressions, but Oshun is a design spec for user-visible syntax and > behavior, and there's no reason at all it would necessarily be implemented > with regular expressions. > > In fact I would assume the opposite, that an Oshun implementation being more > modern would attach to core Perl very closely and exploit directly > everything that Perl::Types would, and have the same performance potential. > > I would expect Oshun to follow the same kind of path Corinna did, which > yielded a very tight and efficient implementation in principle. Why would you expect that? Cheers, Brett > > -- Darren Duncan > -- -- oodler@cpan.org oodler577@sdf-eu.org SDF-EU Public Access UNIX System - http://sdfeu.org irc.perl.org #openmp #pdl #nativeThread Previous | Thread Next