Ivan Smirnov

It looks like it doesn't on nightly, indeed. I'm not sure what the policy is though, an ICE on stable (even though not occurring on nightly) is still an ICE?

(This already exists as a separate function `get_typed_column_writer_mut()` or something like that - it's just it would be nice to have it as method; also that function panics instead of...

@jturner314 That would be the cleanest default, indeed - anything that's already in your .gitignore has to no reason to be watched.

@nbfalcon As you've said it's more of an edge case - it would be nice if you could prevent ignoring (or rather force-watching folders or files), bonus points if it...

> What about all the freshly created file you did not commit yet? Yep, indeed. I'd rather just have it follow .gitignore by default (and maybe have some option of...

@RonnyPfannschmidt @h-vetinari This has been stale for a while, but I've just come across the same issue - how do you 'silently unselect' a test? Are there any new solutions...

As @h-vetinari pointed out, sometimes "not generate" is not really an option, e.g. you have a highly-dimensional grid of parameters and you need to unselect just a few that don't...

@Tadaboody @nicoddemus Not always, as I've mentioned above: > If you have a large highly-dimensional parametrize-grid For instance, ```python @pytest.mark.parametrize('x1', list(range(10)), ids='x1={}'.format) @pytest.mark.parametrize('x2', list(range(10)), ids='x2={}'.format) @pytest.mark.parametrize('x3', list(range(10)), ids='x3={}'.format) @pytest.mark.parametrize('x4', list(range(10)),...

IIUC how pytest works, once you've entered the test function body, it's already too late. So there's not a whole lot of choices really, it probably has to be something...

With #7194 and with all experimental features enabled, wonder why code highlighting for functions is different (i.e. half-disabled) when applying even a dummy attribute macro like this one? ```rust //...