Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support for more than 2 comparision ? #563

Closed
rajeevbarde opened this issue Sep 20, 2024 · 2 comments
Closed

support for more than 2 comparision ? #563

rajeevbarde opened this issue Sep 20, 2024 · 2 comments

Comments

@rajeevbarde
Copy link

Read the doc but cannot find it . Just want to know if comparison of 5 input is possible and show difference ? Example below

input 1 : It's a rainy day and temperature is 25C
input 2: Its a sunny day and temp is 25C
input 3 : It a hot day and temperature is 25C
input 4 : It's a cold night, and temperature is -5C
input 5 : It's a rainy day and temperature is 18C

@ExplodingCabbage
Copy link
Collaborator

ExplodingCabbage commented Sep 20, 2024

No, there's no support for this currently. (It's also not obvious to me what you'd even want the output to look like or what algorithm we'd use for this. I guess maybe something akin to multiple sequence alignment in bioinformatics.)

I'm not sure I'd even want to accept a patch introducing this feature because I'm not sure it would have any overlap with the rest of the features currently in this library. In this way this idea is unlike the recurring request to add support for diffing using the Levenshtein algorithm; at least we can make Myers diffs and Levenshtein diffs return results in the same output format, just with the Myers ones not featuring any substitutions, and so there'd a single function/API with just an optional parameter to choose the underlying diffing algorithm. But this request, for some kind of multiple alignment, would require everything to be created afresh - new functions with different input and output types AND a new diffing algorithm under the hood. I think at that point it ought to live in a different library.

@ExplodingCabbage ExplodingCabbage closed this as not planned Won't fix, can't repro, duplicate, stale Sep 20, 2024
@rajeevbarde
Copy link
Author

thanks for explanation, I am also not sure how the output will look like.

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

No branches or pull requests

2 participants