Skip to content

Code should be provided inside a Playground #1

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

Closed
BalestraPatrick opened this issue Jan 27, 2016 · 2 comments
Closed

Code should be provided inside a Playground #1

BalestraPatrick opened this issue Jan 27, 2016 · 2 comments

Comments

@BalestraPatrick
Copy link
Contributor

Hey!

Great project and idea! I'm a computer science student and I'm sure many developers will find this repo very useful.
I was thinking that maybe it'd be better to provide the Swift code inside a Playground so people can start running an algorithm and play around with it right away. What do you think? 😀

@hollance
Copy link
Member

Thanks!

I might provide playgrounds too, but I also want to keep this readable on the web without having to go into Xcode. Unfortunately, playgrounds are hard to read on the web.

But definitely something to add! :-)

@BalestraPatrick
Copy link
Contributor Author

Sure, sounds good to me!

hollance pushed a commit that referenced this issue Feb 6, 2016
kelvinlauKL pushed a commit that referenced this issue Sep 23, 2016
vincentngo pushed a commit that referenced this issue Mar 9, 2017
vincentngo pushed a commit that referenced this issue Mar 20, 2017
kelvinlauKL pushed a commit that referenced this issue Apr 4, 2017
kelvinlauKL pushed a commit that referenced this issue Jun 20, 2017
kelvinlauKL pushed a commit that referenced this issue Apr 26, 2018
kelvinlauKL pushed a commit that referenced this issue Oct 17, 2018
Changes class to enum and clarifies the reason why a copy is made
richard-ash pushed a commit that referenced this issue Jan 9, 2019
richard-ash pushed a commit that referenced this issue Sep 14, 2019
kelvinlauKL pushed a commit that referenced this issue May 16, 2020
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

No branches or pull requests

2 participants