Date: Fri, 11 Feb 2022 17:37:29 -0500
On Fri, Feb 11, 2022 at 5:28 PM David Blaikie <dblaikie_at_[hidden]> wrote:
> It seems unfortunate to lose some of the portability provided by relative paths to interface definitions when having the metadata file in the include path instead of the library search path
Yes, but, as I mentioned in the previous email, it also means we
ensure that you're getting the metadata to parse the interface unit
that matches the library artifact you're going to consume. I think
that's not an insignificant win.
> It seems unfortunate to lose some of the portability provided by relative paths to interface definitions when having the metadata file in the include path instead of the library search path
Yes, but, as I mentioned in the previous email, it also means we
ensure that you're getting the metadata to parse the interface unit
that matches the library artifact you're going to consume. I think
that's not an insignificant win.
Received on 2022-02-11 22:37:40