Functions disappear when regions are not properly closed

Version: 1.37.0-insider (user setup)
Commit: 0bd57ac9efae79f9eb1aedc3818ebbb570b9bf6b
Date: 2019-08-02T21:22:13.578Z
Electron: 4.2.7
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 6.2.9200

Consider the following code:

Function Test-Stuff_1 {
    #region Description

    #region MISSING END REGION SECTION
    #endregion
}

Function Test-Stuff_2 {
    # Function not visible
}

Function Test-Stuff_3 {
    # Function not visible

    #Delete ticket

    #endregion
}

Function Test-Stuff_4 {
    # Function visible
}

When you select FOLD ALL or press CTRL+K and CTRL+0 you’ll see that two functions are no longer visible:

This made me freak out at first as I thought I’d lost some of my code. The scope for checking opening and closing regions should be limited to the function itself.

[corbob]

But Regions aren’t a part of the language. They’re there to help the developer group things together and collapse things they don’t want to see in the moment. It’s not for the extension to decide if someone’s region layout makes sense.

Further: this is the same behavior you see with the ISE when you minimize the regions:

[rjmholt]

There’s no reason a region can’t start in one function and end in another. In a case like this, if we take an opinion on how bad input works, it will probably break another use case. Comparing this with something like HTML, if you don’t close a tag, everything is subordinate to that, so I think we’re consistent there and this is working by design.