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.

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

Space and Time complexity #112

Open
sumn2u opened this issue Oct 15, 2023 · 4 comments
Open

Space and Time complexity #112

sumn2u opened this issue Oct 15, 2023 · 4 comments
Assignees

Comments

@sumn2u
Copy link
Owner

sumn2u commented Oct 15, 2023

Considering space and time complexity is a significant aspect of programming that ensures code efficiency, scalability, and maintainability. Having a brief introduction to these concepts, followed by example, can greatly benefit JavaScript developers.

@starvader13
Copy link
Contributor

I would love to take this issue.

@starvader13
Copy link
Contributor

starvader13 commented Oct 15, 2023

@sumn2u There are some basic details I want to know before I start working on this.

  • Can I change the chapter numbers as I want to put the complexity chapter after the loops, functions and objects chapter?
  • Till what details should I go into the complexity chapter?
  • Can you tell whether the given structure is satisfactory or not?
en/complexity
├── README.md
├── space-complexity.md
└── time-complexity.md

@sumn2u
Copy link
Owner Author

sumn2u commented Oct 18, 2023

@sumn2u There are some basic details I want to know before I start working on this.

  • Can I change the chapter numbers as I want to put the complexity chapter after the loops, functions and objects chapter?

Yes

  • Till what details should I go into the complexity chapter?

Surface level that gives readers context would be enough.

  • Can you tell whether the given structure is satisfactory or not?
en/complexity
├── README.md
├── space-complexity.md
└── time-complexity.md

Looks good.

@starvader13
Copy link
Contributor

Surface level that gives readers context would be enough.

Will do that. Thanks for the info.

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

No branches or pull requests

2 participants