guest271314 (2019-06-03T02:25:23.000Z)
guest271314 at gmail.com (2019-06-03T02:39:56.761Z)
> but that requires coordination among modules, which is not always possible. the idea is to inline/rollup es-modules that may not have come from same developers (and whom are unaware their es-modules collide w/ others when rolled-up). How do you intend to know the names of the identifiers to import without "coordination", and check for duplicate identifier names and duplicate exports (```SyntaxError: Duplicate export of 'bar'```)? At the previous post the assertion was that multiple inline imports and exports were not possible. Using ```shortName``` resolved that concern. The issue now is an intentional uncoordinated environment where coordination is expected to be self-assembling and automatic. Are there any more undisclosed aspects of the proposal?
guest271314 at gmail.com (2019-06-03T02:39:39.679Z)
> but that requires coordination among modules, which is not always possible. the idea is to inline/rollup es-modules that may not have come from same developers (and whom are unaware their es-modules collide w/ others when rolled-up). How do you intend to know the names of the identifiers to import without "coordination", and check for duplicate identifier names and duplicate exports (```SyntaxError: Duplicate export of 'bar'```)? At the previous post the assertion was that multiple inline imports and exports were not possible. Using ```shortName``` resolved that concern. The issue now is an intention uncoordinated environment where coordination is expected to be self-assembling and automatic. Are there any more undisclosed aspects of the proposal?
guest271314 at gmail.com (2019-06-03T02:33:19.323Z)
> but that requires coordination among modules, which is not always possible. the idea is to inline/rollup es-modules that may not have come from same developers (and whom are unaware their es-modules collide w/ others when rolled-up). How do you intend to know the names of the identifiers to import without "coordination", and check for duplicate identifier names and duplicate exports (a ```SyntaxError: Duplicate export of 'bar'```)? At the previous post the assertion was that multiple inline imports and exports were not possible. Using ```shortName``` resolved that concern. The issue now is an intention uncoordinated environment where coordination is expected to be self-assembling and automatic. Are there any more undisclosed aspects of the proposal?
guest271314 at gmail.com (2019-06-03T02:32:55.040Z)
> but that requires coordination among modules, which is not always possible. the idea is to inline/rollup es-modules that may not have come from same developers (and whom are unaware their es-modules collide w/ others when rolled-up). How do you intend to know the names of the identifiers to import without "coordination", and check for duplicate identifier names and duplicate exports (a ```SyntaxError: Duplicate export of 'bar'```)? At the previous post the assertion was that multiple imports and exports were not possible. Using ```shortName``` resolved that concern. The issue now is an intention uncoordinated environment where coordination is expected to be self-assembling and automatic. Are there any more undisclosed aspects of the proposal?
guest271314 at gmail.com (2019-06-03T02:30:25.087Z)
> but that requires coordination among modules, which is not always possible. the idea is to inline/rollup es-modules that may not have come from same developers (and whom are unaware their es-modules collide w/ others when rolled-up). How do you intend to know the names of the identifiers to import without "coordination", and check for duplicate identifier names and duplicate exports? At the previous post the assertion was that multiple imports and exports were not possible. Using ```shortName``` resolved that concern. The issue now is an intention uncoordinated environment where coordination is expected to be self-assembling and automatic. Are there any more undisclosed aspects of the proposal?
guest271314 at gmail.com (2019-06-03T02:29:53.976Z)
> but that requires coordination among modules, which is not always possible. the idea is to inline/rollup es-modules that may not have come from same developers (and whom are unaware their es-modules collide w/ others when rolled-up). How do you intend to know the names of the identifiers to import without "coordination" and check for duplicate identifier names and duplicate exports? At the previous post the assertion was that multiple imports and exports were not possible. Using ```shortName``` resolved that concern. The issue now is an intention uncoordinated environment where coordination is expected to be self-assembling and automatic. Are there any more undisclosed aspects of the proposal?