timriley on support-component-dirs-with-mixed-namespaces
Avoid freezing components Thes… Add dirs to load path so earlie… Extract Identifier; support mix… (compare)
timriley on support-component-dirs-with-mixed-namespaces
Fix space (compare)
timriley on support-component-dirs-with-mixed-namespaces
Support component dirs with mix… Add test Refactor component building int… and 30 more (compare)
dry-bot on master
[devtools] sync (compare)
Types::Strict::DateTime
initialisation. When I use the "raw" Gem-supplied types to define everything, all is well; when I use a self-defined module constant, I get a NoMethodError
running what looks like the exact same code. Gist with short single-source-file demo code here
DateTime.now
works when using Types::Strict::DateTime.default { DateTime.now }
; it does not work when attempting to use a constant defined as Types::Strict::DateTime.default { DateTime.now }
Types
module you have a clash with Types::DateTime
constant