Skip to content

feat: Make config copyable#57

Open
dmtrKovalenko wants to merge 2 commits intosaghen:mainfrom
dmtrKovalenko:fix/saturating-subs
Open

feat: Make config copyable#57
dmtrKovalenko wants to merge 2 commits intosaghen:mainfrom
dmtrKovalenko:fix/saturating-subs

Conversation

@dmtrKovalenko
Copy link
Contributor

This is literally fixing the pain point of the public API and improves the usage of internal tooling (less explicit dereferences) even though the performance impact is minimal this is very annoying that you need to copy that is anyway stack allocated by the compiler.

Like for example in a loop I can not simply move the frizbee config in the block and modify the options for max typos for example I have to deal with the ownership which sometimes becomes tricky

When I maintain my fork it is hard to pull becuase it is unclear which
version was used to test and build the frizbee. Sometimes new features
are used or some version are just unstable.

I propose to fix the nightly channel in the rust toolchain toml this
and update it accordingly. This will make it easier to maintain
libraries and forks
@saghen
Copy link
Owner

saghen commented Feb 12, 2026

Do you mind sharing some code examples of how it makes it difficult? Losing the ability to use a String is an unfortunate limitation, and I'm worried about adding future values to the Config which wouldn't be Copyable.

@saghen
Copy link
Owner

saghen commented Feb 13, 2026

I've marked any non-alphanumeric as a delimiter in #52 so the String is no longer an issue. It is still quite odd to me having a non-primitive type be Copy in rust though. The code examples would definitely help.

@saghen saghen force-pushed the main branch 3 times, most recently from 30d10ea to efc3f88 Compare February 23, 2026 01:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants