Typos (#4712)
This commit is contained in:
parent
2b70bbed59
commit
ed8610b290
|
@ -60,7 +60,7 @@ Use the above rules.
|
|||
#### Generating the Equals method with `in`
|
||||
|
||||
We looked at a potential optimization around the `Equals` method, where we could generate it with an `in` parameter, instead of
|
||||
with a by-value parameter. This could help scenarios with large struct types get better codegen. However, when we would want to
|
||||
with a by-value parameter. This could help scenarios with large struct types get better codegen. However, when we would want to do
|
||||
this is a very complicated heuristic. For structs smaller than machine pointer size, it is usually faster to pass by value. This
|
||||
gets even more complex when considering types that are passed in non-standard registers, such as vectorized code. We don't think
|
||||
there's a generalized way to do this heuristic. Instead, we just need to make sure that the user can perform this optimization, if
|
||||
|
@ -122,4 +122,4 @@ general string templating system could be interesting, we think that this is a b
|
|||
|
||||
##### Conclusion
|
||||
|
||||
We won't pursuing specific structured syntax at this time.
|
||||
We won't pursue specific structured syntax at this time.
|
||||
|
|
Loading…
Reference in a new issue