Skip to content
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.

Sign up for GitHub

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

Jump to bottom

two-step processing method to two-level processing method? #74

Open
himorin opened this issue Nov 24, 2021 · 6 comments · May be fixed by #84
Open

two-step processing method to two-level processing method? #74

himorin opened this issue Nov 24, 2021 · 6 comments · May be fixed by #84

Comments

@himorin
Copy link
Contributor

himorin commented Nov 24, 2021

In Japanese text, two-step processing method is written as two level. Also, step usually refers each detailed procedure within one process like API implementation.
This could be confusing and we might be better to consider of rewording two-step processing method with level or something.
@himorin himorin mentioned this issue Nov 24, 2021
Merged
@macnmm
Copy link

macnmm commented Nov 24, 2021

Usually we say “two passes” if calculation has to be done multiple times

@himorin
Copy link
Contributor Author

himorin commented Nov 25, 2021

it's not to perform multiple times, but to categorize multiple procedure items into two part - within ruby block and to place inline direction.

@himorin himorin mentioned this issue Nov 25, 2021
Open
@murata2makoto
Copy link

How about "layer"? I cannot live with "pass" or "step".

@himorin
Copy link
Contributor Author

himorin commented Jan 7, 2022

Just note, I've ping to @macnmm on this topic (yesterday) that he would prepare some note, so I expect to have more discussion during our upcoming call (Jan/18). @kidayasuo please include as an agendum.

@himorin himorin linked a pull request Mar 18, 2022 that will close this issue
Open
@kidayasuo
Copy link
Contributor

This one has been resolved it seems?

@himorin
Copy link
Contributor Author

himorin commented Apr 20, 2023

@kidayasuo this is "issue", to be closed by #84

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

replaced two-step processing part himorin/simple-ruby
4 participants
@himorin @murata2makoto @macnmm @kidayasuo