Travis (Oct 12 2022 at 14:07): Travis (Oct 12 2022 at 14:07):is there some way to accomplish this?
contents <- path
|> Path.fromStr
|> File.readUtf8
|> Task.onFail \_ -> Stderr.line "oops" |> Task.await
i get the errors
── TOO MANY ARGS ────────────────────────────────────── platform-test/main.roc ─
The onFail function expects 2 arguments, but it got 3 instead:
20│ contents <- path |> Path.fromStr |> File.readUtf8 |> Task.onFail \_ -> Stderr.line "oops" |> Task.await
^^^^^^^^^^^
Are there any missing commas? Or missing parentheses?
── TOO FEW ARGS ─────────────────────────────────────── platform-test/main.roc ─
The await function expects 2 arguments, but it got only 1:
20│ contents <- path |> Path.fromStr |> File.readUtf8 |> Task.onFail \_ -> Stderr.line "oops" |> Task.await
^^^^^^^^^^
i'm thinking Task.attempt might work
jan kili (Oct 12 2022 at 14:12):Syntax aside, I don't think stderr writing should pipe to a variable named contents... mixing steps?
jan kili (Oct 12 2022 at 14:13):Today you'll need to add parentheses around your mid-pipeline function
jan kili (Oct 12 2022 at 14:14):What type are you aiming for for contents?
Travis (Oct 12 2022 at 14:15):contents is a List u8 i believe
Travis (Oct 12 2022 at 14:16):wait maybe its a Str. next line is:
raw = Str.toUtf8 contents
jan kili (Oct 12 2022 at 14:16):(there is a File.readBytes that you might like)
jan kili (Oct 12 2022 at 14:17):But yes, that sounds like a good aim, for contents to be a str
Travis (Oct 12 2022 at 14:17):yeah i don't really care what type contents is, Str or List u8 is fine. but lets just say Str for now
jan kili (Oct 12 2022 at 14:18):Unfortunately, after File.readUtf8 returns a task that could Ok or Err, you're not handling/extracting either the Ok or Err cases
Travis (Oct 12 2022 at 14:18):this is just for demoing my zig platform
jan kili (Oct 12 2022 at 14:19):I recommend changing contents to result
jan kili (Oct 12 2022 at 14:20):deleting the onFail logic and just awaiting the file read
jan kili (Oct 12 2022 at 14:20):then on a new line handle the result
Travis (Oct 12 2022 at 14:20):ok sounds good. i'll see what i can do.
Travis (Oct 12 2022 at 14:20):thanks!
jan kili (Oct 12 2022 at 14:20):After that works, recombining the lines is still an option but you'll have a working baseline :)
jan kili (Oct 12 2022 at 14:20):You bet!
jan kili (Oct 12 2022 at 14:22):And in case it's a point of confusion, stderr writing isn't a side effect
Travis (Oct 12 2022 at 14:22):hold on. how can i get a Result without stopping the subsequent chain of Tasks? Task.attempt?
Travis (Oct 12 2022 at 14:23):thats what i was trying to use but having some problems. does it sound like it should work?
Travis (Oct 12 2022 at 14:24):maybe you are saying instead of backpassing handle contents in a new function?
Brendan Hansknecht (Oct 12 2022 at 14:25):Shouldn't this work?
contents <- path
|> Path.fromStr
|> File.readUtf8
|> Task.onFail (\_ -> Stderr.line "oops")
|> Task.await
ooh seems closer. now i get an unexpected type error...
Travis (Oct 12 2022 at 14:27):the diff is Task {} vs Task Str
Travis (Oct 12 2022 at 14:27):This 2nd argument to onFail has an unexpected type:
31│ |> Task.onFail (\_ -> Stderr.line "oops")
^^^^^^^^^^^^^^^^^^^^^^^^
The argument is an anonymous function of type:
[FileReadErr Path ReadErr,
FileReadUtf8Err Path [BadUtf8 Utf8ByteProblem Nat]*]* ->
Task {} * [Read [File]*, Write [Stderr]*]a ?
But onFail needs its 2nd argument to be:
[FileReadErr Path ReadErr,
FileReadUtf8Err Path [BadUtf8 Utf8ByteProblem Nat]*]* ->
Task Str * [Read [File]*, Write [Stderr]*]a ?
last line and 4th from last
Travis (Oct 12 2022 at 14:28):seems i just need to return a string there
Brendan Hansknecht (Oct 12 2022 at 14:29):Ah, onFail expects you to return a task that gives you a new value for contents. So a Str
Brendan Hansknecht (Oct 12 2022 at 14:29):So this would work, but doesn't print of coures
contents <- path
|> Path.fromStr
|> File.readUtf8
|> Task.onFail (\_ -> Task.succeed "Some backup content value")
|> Task.await
ah neat. well atleast i'll be able to see that an error happened. this will work ok for my use case.
Travis (Oct 12 2022 at 14:31):thank you both :+1:
Brendan Hansknecht (Oct 12 2022 at 14:31):So the current implementation of onFail doesn't work the way we expected here.
I think you would need to do:
contents <- path
|> Path.fromStr
|> File.readUtf8
|> Task.onFail (\e ->
_ <- Stderr.line "oops" |> Task.await
Task.fail e
)
|> Task.await
Probably would want a different helper function
Brendan Hansknecht (Oct 12 2022 at 14:32):So I guess onFail is really "if I fail, try to recover and continue by doing this"
You want, "if I fail, do this, but stay as a failure"
Brendan Hansknecht (Oct 12 2022 at 14:34):This is probably worth making an issue for, or at least a discussion in #ideas. Seems like a generally useful Task function that we are missing. Also a possible naming confusion/conflict.
Travis (Oct 12 2022 at 14:35):yes. it would be nice to have a helper for that. i agree.
Travis (Oct 12 2022 at 14:36):maybe ill post some of this in ideas in a bit.
Notification Bot (Oct 12 2022 at 14:38):Travis has marked this topic as resolved.
jan kili (Oct 12 2022 at 14:56):That last code snippet works if the file exists (the Ok case), but it panics if it doesn't (the Err case):
thread 'main' panicked at 'not yet implemented: Report a file open error', src/lib.rs:375:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
Aborted (core dumped)
Oh, that's not a roc issue, that's a rust platform issue.
Brendan Hansknecht (Oct 12 2022 at 14:59):The platform doesn't handle all errors yet
Brendan Hansknecht (Oct 12 2022 at 14:59):So some cases it just panics
jan kili (Oct 12 2022 at 15:01):Oh... Oh! I just now understood the "stderr quick exit" approach you two are both taking... that's cool.
Travis (Oct 12 2022 at 15:01):oh reeeeaaalllly? :big_smile: i think i was able to get it working in my zig platform
Travis (Oct 12 2022 at 15:01):$roc platform-test/main.roc -- asfd
🔨 Rebuilding platform...
----
File.readUtf8 platform-test/main.roc:
----
app "platform-main"
packages { ...(truncated)
----
not-a-file: Not Found
like just got it working this morning doing some error handling in roc_fx_fileReadBytes
jan kili (Oct 12 2022 at 15:03):I never realized you could write a backpassing chain that handles early exits halfway through...
jan kili (Oct 12 2022 at 15:03):That's great!
Brendan Hansknecht (Oct 12 2022 at 15:03):I mean the pipelining is handling the early exits. The backpass once triggered would be too late.
Brendan Hansknecht (Oct 12 2022 at 15:04):That said, it is also valid to just accumulate the errors and handle them all at the end in one place.
jan kili (Oct 12 2022 at 15:06): happy <-
input
|> process
|> ifSad exitSadly
|> await
smile <-
happy
|> react
|> ifFrown goToFrownTown
|> await
smile
|> welcomeToSmileTown
Brendan Hansknecht said:
That said, it is also valid to just accumulate the errors and handle them all at the end in one place.
Related to this, if you accumulate all errors, how can you avoid error Tag naming conflict from different lib/package?
jan kili (Oct 12 2022 at 15:08):@Brendan Hansknecht I credit backpassing with this "early escape" functionality, because if you only have |>s with no <- then at the end of the pipeline you'll have to handle a complex multi-type for all possible outcomes.
jan kili (Oct 12 2022 at 15:08):...hence why I was going to suggest changing contents to result and then doing the Err handling after.
jan kili (Oct 12 2022 at 15:10):With <-, you can add mid-pipeline handler steps to narrow the type "returned" by <-, because you're essentially narrowing the branches that the final callback must handle.
jan kili (Oct 12 2022 at 15:11):This might be understood by everyone else here, but it's news to me :D
Travis (Oct 12 2022 at 15:11):related to this, is there a way to get the tag name as a string? or would i just have to do a manual switch?
|> Task.onFail (\_ -> Task.succeed "Not Found") #TODO print error tag somehow
your would just add a lambda to the last await in the pipeline, it would be the same thing with more indentation.
Brendan Hansknecht (Oct 12 2022 at 15:11):manual switch
Brendan Hansknecht (Oct 12 2022 at 15:12):Tag naming conflict from different lib/package?
Wrap them by package or function or etc
Travis (Oct 12 2022 at 15:12):i think i'm spoiled by zig here
Brendan Hansknecht (Oct 12 2022 at 15:12):haha. Sounds reasonable. Zig is a nice language.
Travis (Oct 12 2022 at 15:13):yeah @tagName would be nice here
Brendan Hansknecht (Oct 12 2022 at 15:20):That's something else that could be worth putting in the #ideas stream.
Last updated: Jul 06 2025 at 12:14 UTC