New ':int64' and ':uint64' route path parameters - and - support the new uint64 for MVC (int64 was already supported there) - and - add ctx.Params().GetUint64 (GetInt64 was already there) - and - make the ':int or :number' to accept negative numbers with no digit limit (at low level) and rename the 'app.Macros().Int.RegisterFunc' to 'Number.RegisterFunc' because number can be any type of number not only standard go type limited - and - add alias for ':boolean' -> ':bool'. Finally, Update the examples but not the version yet, I have to provide a good README table to explain the end-developers how they can benefit by those changes and why the breaking change (which is to accept negative numbers via ':int') is for their own good and how they can make their own macro functions so they do not depend on the Iris builtn macro funcs only. More to come tomorrow, stay tuned

Former-commit-id: 3601abfc89478185afec3594375080778214283e

_examples/README.md

@@ -104,7 +104,7 @@ Structuring depends on your own needs. We can't tell you how to design your own
 
 ### Routing, Grouping, Dynamic Path Parameters, "Macros" and Custom Context
 
-* `app.Get("{userid:int min(1)}", myHandler)`
+* `app.Get("{userid:number min(1)}", myHandler)`
 * `app.Post("{asset:path}", myHandler)`
 * `app.Put("{custom:string regexp([a-z]+)}", myHandler)`
 
@@ -128,10 +128,10 @@ app.Get("/profile/me", userHandler)
 
 // Matches all GET requests prefixed with /users/
 // and followed by a number which should be equal or bigger than 1
-app.Get("/user/{userid:int min(1)}", getUserHandler)
+app.Get("/user/{userid:number min(1)}", getUserHandler)
 // Matches all requests DELETE prefixed with /users/
 // and following by a number which should be equal or bigger than 1
-app.Delete("/user/{userid:int min(1)}", deleteUserHandler)
+app.Delete("/user/{userid:number min(1)}", deleteUserHandler)
 
 // Matches all GET requests except "/", "/about", anything starts with "/assets/" etc...
 // because it does not conflict with the rest of the routes.