On Sat, 30 Sep 2017 13:47:22 -0700, allber...@gmail.com wrote:
> So I included at least one discussion in the ticket that was utterly
> pointless and left unread. At this point I'm just going to assume only
> half-exposing the underlying mechanism is considered a feature and I need
> to use a diffe
On Sat, Sep 30, 2017 at 4:35 PM, Sam S. via RT wrote:
> To the extent that you're basing your expectations on the fact that a Perl
> 5 `undef` can be used in ways that a Perl 6 `Failure` cannot (without
> blowing up), well, that's just a matter of having to unlearn Perl 5 (or
> other programming
On Sat, Sep 30, 2017 at 4:35 PM, Sam S. via RT wrote:
> To the extent that you're basing your expectations on the fact that a Perl
> 5 `undef` can be used in ways that a Perl 6 `Failure` cannot (without
> blowing up), well, that's just a matter of having to unlearn Perl 5 (or
> other programming
I agree with Zoffix that this seems to be fine as is.
Generally speaking, IO operations that logically require an existing path will
return a Failure if the path does not in fact exist:
Slurp its content? Failure.
Rename/move/copy it? Failure.
Check its size? Failure.
Check if it is of t
On Fri, 29 Sep 2017 14:43:22 -0700, allber...@gmail.com wrote:
> So, the first problem is that you have to be aware of the special behavior
> of Failure and how it interacts with a method which is documented as
> producing Bool.
That documentation also lists the conditions when the method `fail`s.
On Fri, 29 Sep 2017 14:43:22 -0700, allber...@gmail.com wrote:
> So, the first problem is that you have to be aware of the special behavior
> of Failure and how it interacts with a method which is documented as
> producing Bool.
That documentation also lists the conditions when the method `fail`s.
# New Ticket Created by Brandon Allbery
# Please include the string: [perl #132185]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132185 >
This turns out to be fairly complex, and has implications that may go well
beyond file
