Evgeniy OZ

Because I was able to reach it (unintentionally) and I can't afford whole server crash just because user sent mailformed XML to input. And Result/Option is much more adjustable way.

I use another crate already, so it's not actual issue for me, but I think other users will be glad to control their execution flow.

I use this for effects without params: ```ts someEffect$ = this.effect(_ => _.pipe( ``` and this for effects with params: ```ts someEffect$ = this.effect(_ => _.pipe( ``` ## Full examples...

Ok, 1.0 released, even more, can we please discuss it again? especially default arguments.

> Also, this feature could easily be misused by taking named parameters instead of structs, which, I think, is a bad thing. No, using structs instead of named arguments is...

Really frustrated to see such comments. All modern languages except Go have it, but Rust "don't need it, because macros". What a shame.

> Your functions shouldn't take a large number of arguments anyway. I will decide it, not you. > Structs are strongly typed function arguments too. > Often functions takes a...

It's so ugly... Why just don't let filenames be as they were submitted in CLI? If I want name all my files somethinglikethatandletthembeugly, I just will submit it in CLI......

Of course I can, but automation tools should not require manual fixes... `Having them be mixed case caused more problems.` Non-declared breaking changes in tool, that's what cause problems. I...

@eddiemonge filenames shouldn't follows any hardcoded rules, developer should be able to declare name of file (and controller, directive, service) exactly as he wants. If user will create name pfxRemoteIP...