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
In many scenarios, it is not necessary to create/check .lafl_lock nor to duplicate files (in the form <hash>-<number>). We should allow users to disable this functionality.
The text was updated successfully, but these errors were encountered:
addisoncrump
changed the title
Corpora which store on-disk: skip the generation of .lafl_lock files + duplicates with postfix
Corpora which store on-disk: permit skip the generation of .lafl_lock files + duplicates with postfix
Mar 7, 2023
addisoncrump
changed the title
Corpora which store on-disk: permit skip the generation of .lafl_lock files + duplicates with postfix
Corpora which store on-disk: permit skipping the generation of .lafl_lock files + duplicates with postfix
Mar 7, 2023
What would be the best way to add this option to the API? Adding a new argument to the constructors would have to be a breaking change since Rust doesn't have default arguments yet, and adding new constructors doesn't seem to be ideal since there are already three for InMemoryOnDiskCorpus.
What would be the best way to add this option to the API? Adding a new argument to the constructors would have to be a breaking change since Rust doesn't have default arguments yet, and adding new constructors doesn't seem to be ideal since there are already three for InMemoryOnDiskCorpus.
Sorry, missed that comment.
It might be useful to add a builder at some point, or simply make it a setting on the corpus after creation
Uh oh!
There was an error while loading. Please reload this page.
In many scenarios, it is not necessary to create/check
.lafl_lock
nor to duplicate files (in the form<hash>-<number>
). We should allow users to disable this functionality.The text was updated successfully, but these errors were encountered: