Closed hasezoey closed 9 months ago
refactored for #126, i had to use the double-new
approach, because one of the required options is behind a flag and it would be weird to have to specify a option that has no effect (if feature is off)
EDIT: also added a changelog entry
This PR refactors
GenerationConfig
to supportDefault
where possible by separating out required and optional fields and supporting a top-level builder. (as suggested as point 3 and hybrid-approach of point 3)in addition this PR also:
#[inline]
attribute for opaque / trivial functionsfixes #92