Standard library assertion functions still default to #file rather than #fileID even though SE-0285 is stated as implemented

bobergj · 2022-02-16T06:31:50.674Z

https://github.com/apple/swift-evolution/blob/main/proposals/0285-ease-pound-file-transition.md#detailed-design states the following:

Standard library assertion functions like assert , precondition , and fatalError will switch from #file to #fileID . When a filename is included in a compiler-generated trap, such as a force unwrap, it will also emit a literal equivalent to using #fileID .

But in Swift 5.6, and on the main branch, these functions still have a default argument of #file: https://github.com/apple/swift/blob/main/stdlib/public/core/Assert.swift

Is this an oversight or is it intentional - and instead this change will simply be realized with the change of behaviour of #file in a Swift 6 compiler mode?

benrimmington · 2022-02-17T02:12:04.206Z

The standard library is using a compiler flag, to alias #file as #fileID.

github.com/apple/swift

[Staging] Force stdlib into “Swift 6 mode” for #file

committed 09:06PM - 13 Jul 20 UTC

beccadax

+4 -1

We ultimately want to explicitly change standard library uses of #file to #fileI…D, but once we do, previous compilers won’t be able to build the standard library. So instead, we will temporarily build the standard library with -enable-experimental-concise-pound-file, which should have the same effect, but will back-deploy to compilers going back several months.

I presume that standard library APIs can now be updated.
Or we could wait until Swift 6, as you suggested.