Hash type definition changes method signature?

[mperham]

I'm experimenting with LowType.

I have this:

require "low_type"

[...]

class Something
  include LowType
  def initialize(hash)

Do I need to include that Module everywhere or just require it once? I adjusted the signature like so:

   def initialize(hash: Hash[String => String])

And now I see this when I run tests:

ArgumentError: wrong number of arguments (given 1, expected 0)
    lib/sidekiq/api.rb:1075:in 'initialize'

[maedi]

RE:

Do I need to include that Module everywhere or just require it once?

Yes you need to include it per class, and it's scoped per class. You could probably make it feel a bit more global with inheritance (untested):

require 'low_type'

class Parent
  def self.inherited(child)
    child.include LowType
  end
end

class Child < Parent
  # typed code
end

You can also include it on the main object. Making it global would probably freak people out

I've replicated your "hash: Hash[String => String]" syntax in a test which passes:
https://github.com/low-rb/low_type/blob/main/spec/fixtures/low_hash.rb
https://github.com/low-rb/low_type/blob/main/spec/features/low_hash_spec.rb

I'm now trying to replicate the issue by bundle installing the sidekiq repo itself and setting up redis... if you have a branch to share that would also help

[maedi]

There's a lot of classes and privates in https://github.com/sidekiq/sidekiq/blob/main/lib/sidekiq/api.rb. LowType is setup to handle multiple classes/privates per file but I wonder if it could be that, possibly around initialize itself... will look into