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
I could imagine two variants of the codegen: one optimized for programmer-friendliness, the other optimized for performance. Take this class for example:
For developer-friendliness, it might look like this:
publicclassDataRequirementSort:Element{[JsonProperty("direction")]publicElement<string> Direction {get;set;}[JsonProperty("path")]publicElement<string> Path {get;set;}}internalclassElement<T>{publicElement<string> Id {get;set;}public Extension[] Extensions {get;set;}publicTValue{get;set;}}
For server-side performance, it might look more like this, given that extensions on primitive types are probably exceedingly rare:
I could imagine two variants of the codegen: one optimized for programmer-friendliness, the other optimized for performance. Take this class for example:
For developer-friendliness, it might look like this:
For server-side performance, it might look more like this, given that extensions on primitive types are probably exceedingly rare:
Originally posted by @johnstairs in #2 (comment)
The text was updated successfully, but these errors were encountered: