2022-6-7 7:07 Neil Bowers <neilb@neilb.org> wrote: > This is a retrospective Pre-RFC for a proposal from Curtis, for which he > submitted a draft RFC[1]. We nearly missed it when reviewing proposals > in-flight in our PSC meeting last week, and decided to trigger a discussion > here, to reinforce the process. > > ... > > [1] https://github.com/Perl/RFCs/pull/16 > > I want to hear the haarg' proposal a little more. >There is another model that could be used. could always ignore the return value from the file if the feature was enabled. This is simpler than the previous option, but accomplishes essentially the same thing. It still needs special handling in , but doesn't need to care about an implicit vs explicit return. In practice, the return value from a ed file is not usable for anything. The only impact it will have on perl's behavior is throwing an error for a false value. This is better done by throwing a real error. If there is no real purpose for returning an explicit value, why complicate the model by trying to handle specially? Does this mean changing the behavior of "use", "require", "do" in the "yield_true" feature?Thread Previous | Thread Next