Feat:Code Organization

[SpiralOSS]

Attempt at Code Organization section.

[SpiralOSS]

I didn't bother with the do in modules because of how oddly it behaves (dotnet/fsharp#13905); unless, @bartelink, you have a good example (?). Interested in your input either way.

[bartelink]

Yes, I agree it's ultra niche and not imprtant. It can be shown in the context of a type anyway.

For that, one might contrast

1. a public primary ctor with 3 args that composes two via a let and then does something with the third via a do
2. a private primary ctor that takes one arg, with a 3 arg new() that delegates to it and does the do bit before delegating

Something should show that assembly level attributes get attached to a do() statement though.

(Will review in a bit)

[bartelink]

needs to mvoe to L129

[SpiralOSS]

Sorry, I'm not understanding this comment. Here is lines 127 to 131:

127 Pipe operator `|>` is used to chain functions and arguments together. Double-backtick identifiers are handy to improve readability especially in unit testing:
128
129    let ``square, negate, then print`` x =
130       x |> square |> negate |> print
131

[bartelink]

was saying that there is/was print (square (negate x)), then print x |> square |> negate, then print >> square >> negate
And one of the fns has ' (prime) naming as it was the second.

if you remove the very first one, then the motivaiton for the second is lost
so prob best to move it down and work it into that section

(and consider the flow onward to showing it with >>)

[bartelink]

that follow -> within ?

[SpiralOSS]

"following in the file" ?

[bartelink]

demarcated by :D

I wanted to allude to a namespace being a grouping construct that things logically within the scope of

And pave the way for saying "and if you use namespace again, then it's an entirely separated new scope with nothing carried over"

I guess module and namespace have that aspect in common

[bartelink]

this is a valid example, but very esoteric

I'd say most common usage of rec is people saying "well for this file, I just want to list everything alphabetically, regardless of the fact that it's normally good to put low level stuff first and then have the hihger level stuff at the bottom, with some exceptions where you use and to put some irrelevant dependencies underneath"

So while this does illustrate what it does and how to use it, I dont think it conveys what it's for really, so am pretty conflicted.

[SpiralOSS]

I stole this from MS Learn. I kind of hate it too. The long names get in the way of what's being demonstrated as well.

[SpiralOSS]

I took a walk and realized I'm conflicted because I hate exceptions. :)

[bartelink]

whereas I think it should have a link to https://eiriktsarpalis.wordpress.com/2017/02/19/youre-better-off-using-exceptions/ and https://fsharpforfunandprofit.com/posts/against-railway-oriented-programming/ :P

[SpiralOSS]

Appears, I was hasty on that merge button. Will review this morning.