Skip to content

wstd::main doesn't set exit code on failure #109

Description

@usergood

When using the #[wstd::main] i would expect that an error would set another exitcode than 0.
This beavior is the same right now as tokio::main in a none wasm-application.

Example usage:

use std::error::Error;
use wstd::http::{Body, Client,  Request};

#[wstd::main]
async fn main() -> Result<(), Box<dyn Error>> {
    let request = Request::get("https://non-existing-url.example.com")
        .body(Body::empty())?;

    let _response = Client::new().send(request).await?;

    Ok(())
}

This will return Exit-code 0 when compiled to wasip2 through the wasi-run WIT-interface, and the error form the application will be throwed away between the wit-interface.
Is this the intended behavior?

For example right now i have to do this to make my "main" applications async

use std::error::Error;
use wstd::http::{Body, Client, Request};

fn main() {
    wstd::runtime::block_on(async move {
        if let Err(err) = async_main().await {
            eprintln!("{err}");
            std::process::exit(1);
        }
    });
}

async fn async_main() -> Result<(), Box<dyn Error>> {
    let request = Request::get("https://non-existing-url.example.com").body(Body::empty())?;

    let _response = Client::new().send(request).await?;

    Ok(())
}

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions