jsoref commented on code in PR #38972:
URL: https://github.com/apache/arrow/pull/38972#discussion_r1414203675
##########
cpp/src/arrow/filesystem/azurefs.cc:
##########
@@ -335,7 +335,7 @@ class ObjectInputFile final : public io::RandomAccessFile {
}
return internal::ExceptionToStatus(
"GetProperties failed for '" + blob_client_->GetUrl() +
- "' with an unexpected Azure error. Can not initialise an
ObjectInputFile "
+ "' with an unexpected Azure error. Cannot initialise an
ObjectInputFile "
Review Comment:
I subscribe to Grammarly's view:
https://www.grammarly.com/blog/cannot-or-can-not/
> Don’t use `can not` when you mean `cannot`. The only time you’re likely to
see `can not` written as separate words is when the word “can” happens to
precede some other phrase that happens to start with “not”:
* `Can’t` is a [contraction](https://www.grammarly.com/blog/contractions/)
of cannot, and it’s best suited for informal writing.
* In formal writing and where contractions are frowned upon, use `cannot`.
* It is possible to write `can not`, but you generally find it only as part
of some other construction, such as “not only . . . but also.”
---
MW's write-up is slightly more tolerant, but not particularly different:
https://www.merriam-webster.com/grammar/cannot-vs-can-not-is-there-a-difference
> Both `cannot` and `can not` are perfectly fine, but `cannot` is far more
common and is therefore recommended, especially in any kind of formal writing.
`Can't` has the same meaning, but as with contractions in general, it is
somewhat informal. In some cases, the `not` following `can` is in fact part of
another phrase, such as “not only"; in such instances `can not` is the
appropriate choice.
In general, I'd encourage only using `can not` when it's actually meant in a
case where `cannot` is wrong to call out "this isn't `cannot`, it's `can not
only` (or similar).
> Cannot has been in use since the 15th century. We don’t know why English
speakers thought it’d be a good idea to zip the two words together to form one;
they didn’t seem to see much use in doing the same to do not or is not or have
not.
##########
cpp/src/arrow/filesystem/azurefs.cc:
##########
@@ -335,7 +335,7 @@ class ObjectInputFile final : public io::RandomAccessFile {
}
return internal::ExceptionToStatus(
"GetProperties failed for '" + blob_client_->GetUrl() +
- "' with an unexpected Azure error. Can not initialise an
ObjectInputFile "
+ "' with an unexpected Azure error. Cannot initialise an
ObjectInputFile "
Review Comment:
I subscribe to Grammarly's view:
https://www.grammarly.com/blog/cannot-or-can-not/
> Don’t use `can not` when you mean `cannot`. The only time you’re likely to
see `can not` written as separate words is when the word “can” happens to
precede some other phrase that happens to start with “not”:
* `Can’t` is a [contraction](https://www.grammarly.com/blog/contractions/)
of cannot, and it’s best suited for informal writing.
* In formal writing and where contractions are frowned upon, use `cannot`.
* It is possible to write `can not`, but you generally find it only as part
of some other construction, such as “not only . . . but also.”
---
MW's write-up is slightly more tolerant, but not particularly different:
https://www.merriam-webster.com/grammar/cannot-vs-can-not-is-there-a-difference
> Both `cannot` and `can not` are perfectly fine, but `cannot` is far more
common and is therefore recommended, especially in any kind of formal writing.
`Can't` has the same meaning, but as with contractions in general, it is
somewhat informal. In some cases, the `not` following `can` is in fact part of
another phrase, such as “not only"; in such instances `can not` is the
appropriate choice.
In general, I'd encourage only using `can not` when it's actually meant in a
case where `cannot` is wrong to call out "this isn't `cannot`, it's `can not
only` (or similar).
> Cannot has been in use since the 15th century. We don’t know why English
speakers thought it’d be a good idea to zip the two words together to form one;
they didn’t seem to see much use in doing the same to do not or is not or have
not.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
