Should warnings be fixed?

[vasily-kirichenko]

There are a number of bugs (or features?) in the codebase, like this one:

https://github.com/Horusiath/Akkling/blob/master/src/Akkling/ActorRefs.fs#L28-L41

Is it worth to make a PR with fixes, or you are aware of them and the code is just WIP?

[Horusiath]

In general, we could attach some fslint rules and start to treat warnings as errors.

In this specific case I think, we should probably drop AskResult<> at all. It's always associated with bind over async computation. AFAIK most of the users expect that ask should just return object of an expected type on success, or throw an exception otherwise.

But this would come with another problem, because while try/with works well in actorOf given behaviors, actor { ... } computation expression fails to tail rec that actor (due to lack of trampolines, see #54).