Skip to content

Delete WasmBinaryBuilder::mappedGlobals (NFC)#2098

Merged
aheejin merged 1 commit intoWebAssembly:masterfrom
aheejin:global_index
May 12, 2019
Merged

Delete WasmBinaryBuilder::mappedGlobals (NFC)#2098
aheejin merged 1 commit intoWebAssembly:masterfrom
aheejin:global_index

Conversation

@aheejin
Copy link
Copy Markdown
Member

@aheejin aheejin commented May 12, 2019

It doesn't seem to be used anywhere and I don't know why the
implementation for WasmBinaryBuilder::getGlobalName and
WasmBinaryBuilder::getFunctionIndexName are different. Renamed
getFunctionIndexName to getFunctionName for consistency.

It doesn't seem to be used anywhere and I don't know why the
implementation for `WasmBinaryBuilder::getGlobalName` and
`WasmBinaryBuilder::getFunctionIndexName` are different. Renamed
`getFunctionIndexName` to `getFunctionName` for consistency.
@aheejin aheejin requested a review from kripken May 12, 2019 06:05
Copy link
Copy Markdown
Member

@kripken kripken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Very good to clean this up.

I think this looked like it did because we used to have separate Import objects, so handling globals and functions was tricky. But then we moved to functions and globals objects that represent either an imported or a defined function or global. And I guess we forgot to clean up the globals code here.

@aheejin aheejin merged commit a1ff274 into WebAssembly:master May 12, 2019
@aheejin aheejin deleted the global_index branch May 12, 2019 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants