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
@jckarter It looks like SILGen is a little too happy to set `overrideLocationForMagicIdentifiers` here. I'm not sure if that means Sema needs to handle the literal expansion here or if overrideLocationForMagicIdentifiers should be unset here. The tests mention something about "not leaking details about the source' so I'm wary of getting rid of it altogether.
I'm not sure what the comment would be referring to, since #file kind of fundamentally "leaks details about the source". I don't see why a string interpolation would be any worse than a bare #file in that regard.
If#file within an interpolation expanded to the name of the callee's file rather than the caller's—which I suspect it would—and if we put default argument evaluation in the caller instead of the callee—which we intend to—then the comment would make sense. But the behavior would remain not what the user would expect.
Additional Detail from JIRA
md5: e16b6eb5c97868b70239d2d1d9c5bc0b
is duplicated by:
Issue Description:
Example:
I'm not sure if this is expected or not, but if it is I guess it would be ideal to not allow #file to be used here.
The text was updated successfully, but these errors were encountered: