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
How about introducing a predefined layered API (say std:test) for testing Layered API infrastructure?
std:test does something (i.e. has a side effect when evaluated), such as incrementing a global variable.
This can be used for example:
When std:test|https://fallbackA.com/ and std:test|https://fallbackB.com/ are imported, then std:test should be evaluated only once. In other words, this is testing that std:x|y resolution happens before module map and the key in the module map is std:x, not std:x|y.
Also, this can be used to test that importing std:x actually works (i.e. evaluates std:x's script) in a simple fashion.
The text was updated successfully, but these errors were encountered:
How about introducing a predefined layered API (say std:test) for testing Layered API infrastructure?
std:test does something (i.e. has a side effect when evaluated), such as incrementing a global variable.
This can be used for example:
std:test|https://fallbackA.com/
andstd:test|https://fallbackB.com/
are imported, thenstd:test
should be evaluated only once. In other words, this is testing that std:x|y resolution happens before module map and the key in the module map is std:x, not std:x|y.Also, this can be used to test that importing std:x actually works (i.e. evaluates std:x's script) in a simple fashion.
The text was updated successfully, but these errors were encountered: