Jira (PUP-7249) Automatic coercion of String to SemVer/SemVerRange

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on PUP-7249   Re: Automatic coercion of String to SemVer/SemVerRange When you actually want to differentiate - for example accept a version or the string "latest". This would be a general mechanism so you end up on a slippery slope - did the user actual mean one or the other? And we end up in the number vs. string, boolean value vs. boolean string etc. (Just go through the fun and games that happen if you start dealing with Booleans in String form and auto conversion). We would quickly be back at the wonky 3.x rules for type conversion (also see the classic WAT presentation regarding _javascript_). I can imagine adding automatic conversion when explicitly requested, but doing it everywhere for all values will create more problems than it solves. Part of me does not want to add this as it makes argument passing and parameter matching even more complicated - instead we should make it easier to deliver data of the correct type (i.e. it is a hiera/data issue, and not an issue of automatic type conversion). The Initializer[T] variant would provide automatic checking, but would not instantiate - thus the logic can rely on it being done and simply do something like: class myclass(Variant[SemVer, Initializer[SemVer]] $ver) { $actual_ver = SemVer($ver) # would always work as automatic type checking makes sure of that } Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.