sys.FileStat.ctime updated with more accurate file creation time #1063
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Linux: Uses statx syscall for this field only to get stx_btime.tv_sec
macOS: Still uses the existing stat syscall, but accesses the macOS-only st_birthtime field instead
Historically, the POSIX standard did not require file systems to store the file creation time at all, so the stat syscall did not provide it. Modern file systems now store this value, and different operating systems provide it in different ways. The previous value of ctime from the stat syscall is actually the "status change time". This value may initially match the file creation time, but it can be updated after the file is modified in certain ways (including the file size changing, which is very common). The new value is more accurate, better matching how Haxe documents this field.