Tooling-added opens are placed above top-level #-directives in scripts when top-level insertions are set

[cartermp]

See the following:

Since the setting for inserting suggested open statements is set to top-level, it places it at the top of the file.

However, it could be argued that #r/#load-directives are special, and "top-level" open statements should go below them.

Note that if top-level is not set in settings, then it will place open statements below these declarations. However, this will also place opens within the nearest scope.

[kevmal]

Perhaps it's a separate issue but I consider it a bug since the "fix" introduces an error, namely, opening a namespace before the assembly is referenced. Meanwhile visual studio sees no error even though it'll fail once sent to FSI.

This looks all good:

This is what happens when sent to FSI:

Script7.fsx(1,17): error FS0039: The namespace 'Linq' is not defined.

[cartermp]

Thanks for the example, labeling as a bug

[cartermp]

@dsyme I've bumped this up from low severity. With package references in scripts we're likely to see a lot more scripting since it'll be so much easier to just reference stuff and go to town on it. If it weren't for package references I'd say low severity is fine

[psfinaki]

Okay I created a separate issue for the FSI thing since, as of now, the behavior is inconsistent regardless of the order of the open and #r lines.

This one holds for the original problem but feels more as an improvement, since at least VS can compile the "fixed" version.