Use the new DuckDB lambda syntax to avoid the deprecation warning#23
Open
DS-argus wants to merge 1 commit intowylie102:mainfrom
Open
Use the new DuckDB lambda syntax to avoid the deprecation warning#23DS-argus wants to merge 1 commit intowylie102:mainfrom
DS-argus wants to merge 1 commit intowylie102:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi, and thanks for this plugin — it has been really nice to use.
While using it on Windows with Yazi 26.1.22 and DuckDB 1.5.0, I noticed DuckDB now emits this warning during preview:
WARNING: Deprecated lambda arrow (->) detectedThis PR updates the remaining lambda expression in
main.luafrom the old arrow form to the currentlambda ... : ...syntax:c -> list_contains(...)lambda c : list_contains(...)As far as I can tell, this does not change behavior and just removes the warning on newer DuckDB versions.
If you'd prefer a different wording or style here, I'm happy to adjust it.