top | item 19698369

(no title)

mnarayan01 | 6 years ago

The parser thinks that's a block not a hash.

discuss

order

cutler|6 years ago

Right, so why not implement the sig as a block and keep the syntax concise - the Ruby Way.

bhuga|6 years ago

The sigs are implemented as blocks.

We had them as hashes for a while, but it meant that code in all sigs was loaded as the code was loaded, even if runtime typechecking was disabled. We were forced to load all constants in any signature in a file, an effect which cascades quickly. It had a big impact on the dev-edit-test loop.

For example, if we're testing `method1` on `Foo`, but `method2` has a sig that references `Bar`, we'd have to load `Bar` to run a test against `method1`.

Now sigs are blocks and lazy, and we pay that load penalty the first time the method is called and a typecheck is performed.

mnarayan01|6 years ago

Then you'd need an extra set of delimiters, e.g.:

  sig {{name: String, returns: Integer}}