You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For what I found looks like starting from Go 1.12 it really guarantee a stable iteration order over map keys. Which only means the iteration order would be the same among any other iteration.
But I didn't find any confirmation that the iteration order really preserve the order keys were defined on creation or added after.
As a hash map I believe the order might even depend on a keys number in it.
From the other hand the order of [url ] sections in a config are critically matters for the way rules would be matched/applied during resolution.
Currently Config.URLs is represented as a
map
.For what I found looks like starting from Go
1.12
it really guarantee a stable iteration order over map keys. Which only means the iteration order would be the same among any other iteration.But I didn't find any confirmation that the iteration order really preserve the order keys were defined on creation or added after.
As a hash map I believe the order might even depend on a keys number in it.
From the other hand the order of
[url ]
sections in a config are critically matters for the way rules would be matched/applied during resolution.So is it really the right structure for
URLs
?Related #863
The text was updated successfully, but these errors were encountered: