in vs inout
arm.plus at gmail.com
Thu Apr 30 14:00:40 UTC 2020
The recent change log for v2.092.0 Beta says that with the new
implementation for the `in` storage class:
> `in` should be the storage class of choice for purely input
> function parameters.
I had been using inout for some time now for "purely input
function parameters". Is there a case to be made in favor of
const? why would be scope const preferred over scope inout?
More information about the Digitalmars-d-learn