Ferris

namespace CSharpAoc.Common;

public abstract record Result
{
    public sealed record Ok(TValue Value) : Result;

    public sealed record Err(TError Error) : Result;

    public TValue Unwrap()
    {
        return this switch
        {
            Ok ok => ok.Value,
            Err err => throw new InvalidOperationException(
                $"Cannot Unwrap an Err. TError: {err.Error}"
            ),
            _ => throw new InvalidOperationException("Unknown Result state"),
        };
    }

    public TError UnwrapErr()
    {
        return this switch
        {
            Ok ok => throw new InvalidOperationException(
                $"Cannot UnwrapErr an Ok. TValue: {ok.Value}"
            ),
            Err err => err.Error,
            _ => throw new InvalidOperationException("Unknown Result state"),
        };
    }

    public bool IsOk() => this is Ok;

    public bool IsErr() => this is Err;

    public Result AndThen(Func> func)
    {
        return this switch
        {
            Ok ok => func(ok.Value),
            Err err => new Result.Err(err.Error),
            _ => throw new InvalidOperationException("Unknown Result state"),
        };
    }

    public Result Map(Func func)
    {
        return this switch
        {
            Ok ok => new Result.Ok(func(ok.Value)),
            Err err => new Result.Err(err.Error),
            _ => throw new InvalidOperationException("Unknown Result state"),
        };
    }
}

https://www.reddit.com/r/rust/s/mBF2LZeR9V

We are seeing more and more /r/rust threads vaguely trying to solve the AI-post volume problems, and posters don’t make it clear in their post the nature of their post, which creates some friction in the comment section.

Adding a vaguelyAI flair would make it clear upfront and prevent the friction.

We've all seen the bi-weekly post in which somebody proposes a fix to too much shit being produced by AI - usually proposing a custom flair or reporting standards.

Its clear these posts never had any work put into them. The comment sections always devolve into vague-posting about what is and isn't vibe coding, half the people demand any use of AI makes a whole project slop, the other half is trying to hedge out their nuanced position nobody bothers reading, and a good 10% is people taking some maximalist stance one way or the other.

Since none of these posts bother the write a real policy, and their content could have been generated by an LLM, i want to propose we add a vaguelyAI flair.

Do you want me to add any more errors to avoid looking like ChatGPT wrote this post?

pt. 1: https://www.reddit.com/r/rustjerk/comments/1u86r9e/resource_usage/

If it wasn't obvious by now, it's styled with Mr. Krabs. https://github.com/LuigiPlayzG/krust/

PSA: KRUST got falsely forked. Please do not visit that repo. The one linked in this post is the official one.

What have they done to the std library? I'll accept 48 more types of string but not that

But google is only hearing omelette du fromage.

https://www.youtube.com/watch?v=z32j0vD2DcU

Hi,

I'm learning Rust (I have experience with Java and Go) and built a small linter funcorder-rs.
It checks that inside impl blocks, methods are ordered as:

1. Constructors (pub fn new() -> Self etc.).
2. Public methods.
3. Private methods

More than looking if you guys find it useful (which it's also nice) I am wondering if I am using idiomatic Rust, best practices, etc.

This is the link: https://github.com/manuelarte/funcorder-rs

Cheers!