Various small tickets...

[jdunkerley]

Pull Request Description

• Added Text.length into Text class so CB lists the built in.
• Added File.starts_with and tests for the built in method.
• Add to_js_object and to_display_text to Regex.
  
• Add to_js_object and to_display_text to Match.
  
• Remove the bit_shift_l alias from the built-ins.
• Add test and Enso wrapper for Text.is_normalized.

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• All code has been tested:
  • Unit tests have been written where possible.
  • If GUI codebase was changed, the GUI was tested when built using ./run ide build.

[GregoryTravis]

contains or starts_with? If it has a ** in the middle but not at the start, will it still work right?

[jdunkerley]

if it has ** in the middle I am trusting you know what you are doing!

[JaroslavTulach]

Advanturous! Static method is builtin, but instance method not and delegates to the static one. I am suprised it works. But if it does, then OK.

[radeusgd]

I think I don't understand, where is a static method here?

[radeusgd]

This case looks slightly worrying. If I understand correctly what happens, it will be prepended with **. So now it will find all paths that have >= 3 layers of nesting, whereas before this change it would only find paths that have == 3 layers of nesting.

Looking at the call, I'd indeed expect == 3 to be the correct behaviour here.

I appreciate the change, as indeed the other tests that you added show it was needed - specially the one just below - indeed if recursive=True, it's nice to find the file in all subdirectories. But it can break some usages for more advanced use cases. I'm not sure if we can do anything good about it though... It is not great that we cannot now use this method to find == n layers of nesting - we will always find arbitrarily nested files. On the other hand, maybe it's not that important - I think overall this change is a pragmatic improvement.