It looks like not calling to canImportGlobalVar during attribute propagation doesn't break any tests. Also, technically speaking, whether or not object can be imported shouldn't affect its readonly property
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
Given the write only bug that popped up with the earlier patch, I'm wondering if this is safe. I.e. we must import a global variable if we have marked it as write only, so if we don't import it later (because it fails one of the legality checks in canImportGlobalVar), then we can end up in trouble.