New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is means digest in ECMAScript document? #1197

Open
dSalieri opened this Issue May 19, 2018 · 6 comments

Comments

Projects
None yet
4 participants
@dSalieri

dSalieri commented May 19, 2018

If you open Module section, you will be able to see:

Its fields contain digested information about the names that are imported by the module and its concrete methods use this digest to link, instantiate, and evaluate the module.

What is mean digest?
P.S Word digest used only in Module section.

@ljharb

This comment has been minimized.

Show comment
Hide comment
@ljharb

ljharb May 20, 2018

Member

"digest" means "to arrange in convenient or methodical order; reduce to a system; classify."

The text says that Source Text Module Records have fields that contain "digested information", meaning, information that was classified and arranged methodically. As a noun, "digest" means "a collection or compendium, usually of literary, historical, legal, or scientific matter, especially when classified or condensed." - so, it's saying that the concrete methods use the "collection of information" to link, instantiate, and evaluate the module.

Member

ljharb commented May 20, 2018

"digest" means "to arrange in convenient or methodical order; reduce to a system; classify."

The text says that Source Text Module Records have fields that contain "digested information", meaning, information that was classified and arranged methodically. As a noun, "digest" means "a collection or compendium, usually of literary, historical, legal, or scientific matter, especially when classified or condensed." - so, it's saying that the concrete methods use the "collection of information" to link, instantiate, and evaluate the module.

@dSalieri

This comment has been minimized.

Show comment
Hide comment
@dSalieri

dSalieri commented May 20, 2018

@ljharb

This comment has been minimized.

Show comment
Hide comment
@ljharb

ljharb May 20, 2018

Member

@dSalieri no, a UUID would be a single unique identifier; in this case the "digest" is a collection of key/value pairs.

Member

ljharb commented May 20, 2018

@dSalieri no, a UUID would be a single unique identifier; in this case the "digest" is a collection of key/value pairs.

@dSalieri

This comment has been minimized.

Show comment
Hide comment
@dSalieri

dSalieri May 20, 2018

@ljharb So I can translate "digested" as "processed" and "digest" as "processed data"?

dSalieri commented May 20, 2018

@ljharb So I can translate "digested" as "processed" and "digest" as "processed data"?

@allenwb

This comment has been minimized.

Show comment
Hide comment
@allenwb

allenwb May 20, 2018

Member

I wrote the original sentence that used "digested":

So I can translate "digested" as "processed" and "digest" as "processed data"?

I think a better translation would be: "digested" as "extracted" and "digest" as "the extracted data"; because the information isn't is actually transformed. It is just collected. In English, "process" could imply that the information has been manipulated in some way.

The "digested information" exists in the source code of a module and could be obtained each time it is needed by reanalyzing the source code. But its easier in the specification to make reference to the digested information than it is describe how to analyze the source code each time some information is needed

Member

allenwb commented May 20, 2018

I wrote the original sentence that used "digested":

So I can translate "digested" as "processed" and "digest" as "processed data"?

I think a better translation would be: "digested" as "extracted" and "digest" as "the extracted data"; because the information isn't is actually transformed. It is just collected. In English, "process" could imply that the information has been manipulated in some way.

The "digested information" exists in the source code of a module and could be obtained each time it is needed by reanalyzing the source code. But its easier in the specification to make reference to the digested information than it is describe how to analyze the source code each time some information is needed

@dSalieri

This comment has been minimized.

Show comment
Hide comment
@dSalieri

dSalieri May 20, 2018

@allenwb Can you show example of "digested information" in the source code of a module? I can not yet imagine this abstraction.

dSalieri commented May 20, 2018

@allenwb Can you show example of "digested information" in the source code of a module? I can not yet imagine this abstraction.

@jmdyck jmdyck added the question label Sep 14, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment