Jira (PUP-5816) Allow puppet type system types to be used in case expressions by supporting === to mean instance?

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg created an issue   Puppet / PUP-5816 Allow puppet type system types to be used in case expressions by supporting === to mean instance? Issue Type: Improvement Assignee: Unassigned Created: 2016/02/03 11:07 PM Priority: Normal Reporter: Henrik Lindberg It would be handy to support === on PAnyType as that makes it possible to directly use instances of puppet types in ruby case expressions. With this method on PAnyType: def ===(o) instance?(o) end And some constants like these: NOT_NIL = PNotUndefType::DEFAULT TUPLE = PTupleType.new( [NOT_NIL, NOT_NIL] ) FIRST = PTupleType.new( [NOT_NIL, nil] ) SECOND = PTupleType,new( [nil, NOT_NIL] ) {code)   You can easily handle the otherwise awkward testing of two complex expressions against nil. {code:ruby} def example(a, b) if a && !b puts "a but not b" elsif !a && b puts "not a but b" else puts "both a and b" end can be replaced by: def example(a, b) case [a,b] when FIRST puts "a but not b" when SECOND puts "not a but b" else puts "both a and b" end end The example above just shows the principle. If a and b are complex expressions, they have to be repeated, or assigned to temporary variables. Also if the matching is something that is more advanced than just nil?, or where there are three variables the logic becomes a lot messier, but will be very clean with the puppet type system === operator. Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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.