6 ms·
Sometimes a procedural approach is better for certain (in my opinion, limited) problems. I'd rather use a procedural language for those cases. Also, the .NET
by edgyswingset 12y ago
Sometimes a procedural approach is better for certain (in my opinion, limited) problems. I'd rather use a procedural language for those cases.
Also, the .NET libraries we end up using were, to my knowledge, written in C#. Sometimes interacting with them feels awkward if done functionally.
- MichaelGG 12y agoFortunately, F# does OO and procedural pretty well, so you shouldn't feel pressure to use a functional style if it doesn't fit. I noticed that was something certain folks tended to do, they'd insist on creating an expression as a series of folds and maps, even if it had a very simple expression otherwise (as a list comprehension or simple for..in loop). Cast those cares aside, and write what is most useful for your use case. Sometimes though, you do want break/goto/continue, although in most cases I think such code is better off in C or Rust.