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
We had to add .truncate(false) to our tempfile opening code in #1988 to fix a new Clippy lint. .truncate(false) is equivalent to the previous behavior, but it seems like it would make more sense to use truncate(true). However, when I tried truncate(true), some tests failed.
Perhaps, we should be using truncate(true), and we in fact have a bug here.
The text was updated successfully, but these errors were encountered:
After investigating, I determined that truncate(false) provides the desired behavior, after all. I will prepare a PR to add comments to document why this is the case.
In #1988, we added an explicit call to `truncate(false)` in our `TempFile` code to resolve a new Clippy lint. This call maintained the code's existing behavior, but [seemed like it may not have been the desired behavior](#1988 (comment)), so we opened #1989.
After investigating, we found that the `truncate(false)` call indeed provides the desired behavior.
Here, we add some comments to clarify why we use `truncate(false)` in our code.
Resolves#1989.
We had to add
.truncate(false)
to our tempfile opening code in #1988 to fix a new Clippy lint..truncate(false)
is equivalent to the previous behavior, but it seems like it would make more sense to usetruncate(true)
. However, when I triedtruncate(true)
, some tests failed.Perhaps, we should be using
truncate(true)
, and we in fact have a bug here.The text was updated successfully, but these errors were encountered: