I sent a message to Topps support when I did not get the guaranteed 1 st pack OE several drops back . After a few days they sent a message saying something to the effect of it was my fault somehow , or some BS . I didn ' t care enough to push the issue . Honestly , that just made me loose interest in yet another chase set . <| sep |> People who argue on the Internet in a nutshell <| sep |> Taking a peak behind the curtain , there is usually a different mood in there . Here is verification of the chatlog together with outing of the whistleable . <| sep |> I don ' t think that addresses the issue . Say you have func rangex i 32 , to y i 32 But say , you realize to is wrong word . And you want to change it toend . Like so func rangex i 32 , end yi 32 What happens to range 3 , to 4 ? It becomes a compilation error . Plus using different externalinternal name is a really weird and aesthetically displeasing thing . It ' s forces code writer to keep a mapping of what are his internalexternal variables . One solution could be to allow method overloading . So range 3 , to 4 gets deprecated and points to range 3 , end 4 which is added , not substituted . But method overloading is even less likely to be accepted . One solution that seemed ok was func rangex i 32 , pub end i 32 Which just said , end is now part of your public interface . Deal with it . I mean , I ' d personally love to have defaultnamed arguments . But I definitely could see why it would be a problem . Perhaps using only name arguments as hints is the way to go .