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
I'm not sure what I should expect if attempting to explicitly watch the same file twice; it might be reasonable to either return an error from watch?
edit: I'm now wondering if this crash isn't due to modifying the underlying cfarray during iteration (here) , and ending up out of bounds.
I can put together a PR for this, but I wonder if we shouldn't also have some clearer expectations around how to behave with duplicate entries? Since this is going to be (likely) very implementation dependent, I suspect we should disallow it? I'll defer to @passcod on that.
The text was updated successfully, but these errors were encountered:
My plan would be more to silently ignore duplicate paths. This is how it's shaping up to be in the next version. ("frontend" would never pass overlapping or duplicate paths to "backend")
@passcod sounds good. I expect to be making quite extensive use of this crate in xi over the next little while, and I should have some downtime in december; if you're doing a rewrite and want a hand with anything feel free to ping me.
Thanks — If you subscribe to the discussion in #117... I might not follow that design precisely but I'll chime in there when I'm getting to it seriously.
The following snippet consistently crashes for me:
I'm not sure what I should expect if attempting to explicitly watch the same file twice; it might be reasonable to either return an error fromwatch
?edit: I'm now wondering if this crash isn't due to modifying the underlying cfarray during iteration (here) , and ending up out of bounds.
I can put together a PR for this, but I wonder if we shouldn't also have some clearer expectations around how to behave with duplicate entries? Since this is going to be (likely) very implementation dependent, I suspect we should disallow it? I'll defer to @passcod on that.
The text was updated successfully, but these errors were encountered: