But that's not how overloading in this case would work, as proposed by evacchi. If the function performs a different action depending on whether the value is nil or not, it might require totally different function to handle that case. Otherwise, putting the logic to adquire this value in a different function saves you an import and bloated code. I'd rather write a second function than import options, some(5) everytime.
- optional int parameters for a proc jlp765
- Re: optional int parameters for a proc LeuGim
- Re: optional int parameters for a proc bluenote
- Re: optional int parameters for a proc def
- Re: optional int parameters for a proc evacchi
- Re: optional int parameters for a proc Udiknedormin
- Re: optional int parameters for a p... Arrrrrrrrr
