5 ms·
> An unstable sort could provide this result, but could also give this answer too: It might just be me, but using "this" twice in the same sentence to refer to
by kbenson 9y ago
> An unstable sort could provide this result, but could also give this answer too:
It might just be me, but using "this" twice in the same sentence to refer to two distinct items, one a prior example and one an upcoming example, is somewhat odd. That said, I understood it perfectly fine, it just caused me to stop and ponder the wording for a moment. The following might be more clear:
An unstable sort could provide that result, but could also give this answer too:
- steveklabnik 9y agoSounds great, I've made the change. Thanks! https://github.com/rust-lang/blog.rust-lang.org/commit/92031b9f4c7783c7442da421223a6ef3325738f3 https://github.com/rust-lang/blog.rust-lang.org/commit/92031...
- coldtea 9y agoWell, while you're at it, "also" and "too" perform the same role there. So that phrase could be shortened to "but it could also give this answer".
- evincarofautumn 9y agoIn case anyone’s curious, this is called discourse deixis[1]. It’s a frequent source of errors for non-native English speakers, because in many languages, you use “that” to refer to an example that follows, but English is unusual in that it generally uses “this” for the future and “that” for the past. So that[2] sounds wrong: This[3] probably screwed you up. The somewhat confusing thing is that “this” is also used for the present or recent past, especially in more formal writing. [1]: https://en.wikipedia.org/wiki/Deixis#Discourse https://en.wikipedia.org/wiki/Deixis#Discourse [2]: The following example [3]: The previous sentence
- JoshTriplett 9y ago> English is unusual in that it generally uses “this” for the future and “that” for the past. I don't know that I'd describe it as "future" and "past"; it's more that English uses "this" for "current" and "that" for "other", whether past or future. For instance, "this situation is broken, that solution looks promising" uses "this" to refer to the present and "that" for the future.
- evincarofautumn 9y agoI was referring to past/future in the text. Deixis is about how words and phrases like “this”, “that”, “here”, &c. are contextualised. Your example is unrelated to discourse deixis because it’s not referring to a piece of the surrounding discourse. We use different forms of deixis and spatial metaphors for time, like “the end is near” or “the past is behind us”—in some languages, the past is in front of you (mnemonic: you can see it) while the future is behind (you can’t).
- JoshTriplett 9y agoAh, fair enough; I hadn't interpreted your previous comment as backwards/forwards in the text. Thanks for the clarification.
- mikeash 9y agoWow, nice example. It's so good I initially thought I had completely missed something or your comment had suddenly become incoherent.
- LambdaComplex 9y agoSince you apparently know stuff about language, maybe you can help me out: Sometimes novice programmers try something like "foo == bar && baz" when they really should have "foo == bar && foo == baz". This is because, in English, "Foo is equal to bar and baz" means (and is more common than) "Foo is equal to bar and foo is equal to baz". There's some name for this rule, but I haven't been able to remember it for a while. I think it's "right hand ______", but I can't remember that final word.
- evincarofautumn 9y agoFirst, I have a little anecdote about that. I was at a summer camp where we were taking game programming classes. I had been programming for longer than the other students, so I would help them out. One of my peers asked me for help with a part of his program. In the course of that, I noticed that he had written “if (x == 1 || 2 || 3 || …)” in another part of his code, and explained that this condition would always be true (in C++). He became defensive and dismissed me, saying “nah, I tried it and it works”…because he had only been trying the success cases. It absolutely infuriated me! Anyway, IIRC that pattern is called “conjunction reduction”: “foo equals bar and foo equals baz” becoming “foo equals bar and baz”. The term you might be thinking of is “right node raising”[1], which is when the elements of a conjunction “share” the stuff that follows them, as in “bar equals, and baz equals, foo”. [1]: https://en.wikipedia.org/wiki/Right_node_raising https://en.wikipedia.org/wiki/Right_node_raising
- LambdaComplex 9y agoYes, "right node raising" is exactly what I was looking for. Thank you!