Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Remove the foreign link description and forward to the foreign error #16
As I was writing it though my brain was telling me, 'come on just do it backwards compatibly'. How hard do you think it would be to make the macro optionally parse that string and just discard it?
Just discard it? It wouldn't be hard at all, but it would prevent users from discovering the change to the underlying library functionality. Users could potentially continue working with the faulty assumption that their display string was being used, which I think is worse than the minimal API breakage. Considering they're already bumping the version in order for the API change to occur, it doesn't seem like too much to ask that they just delete the description string.