-
Notifications
You must be signed in to change notification settings - Fork 40
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
Issue for isdisjoin() #36
Comments
It looks as if Markdown has mangled your examples, but I think you were asking why this happens:
And yeah, that's a bug. Drilling down slightly we get:
which are clearly both incorrect. Leave this with me... |
qntm
added a commit
that referenced
this issue
Apr 18, 2018
Fixed with 984b060. Go get |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I am seeing the following output.
However, I can verify that:
Am I misinterpreting the semantics of the isdisjoint() method, or is this a bug.
Some background info: I have a similar motivation to yours, I'm interested in the intersection of two regular expressions. However, I am really only interested in knowing whether this intersection is empty. Is there a more efficient way to doing this than calculating 'parse(rx1) & parse(rx2)' and checking if it is empty? I am really trying to to check if two regular expressions that describe file system paths will overlap to some degree.
The text was updated successfully, but these errors were encountered: