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

Docs example unclear #362

Open
Esqarrouth opened this issue Jan 13, 2017 · 3 comments
Open

Docs example unclear #362

Esqarrouth opened this issue Jan 13, 2017 · 3 comments

Comments

@Esqarrouth
Copy link
Owner

Esqarrouth commented Jan 13, 2017 •
edited
Loading

"I really wonder why someone would prefer array.get(1) over array[1]. (1st example in Readme)"

Read this in reddit, should make the benefits more clear
@piv199
Copy link
Collaborator

piv199 commented Jan 13, 2017

Are there any array[safe: 1] or array.safe[1]? This would really be better than array.get(at: 1) :)

@Khalian
Copy link
Collaborator

Khalian commented Feb 5, 2017

@piv199 Does the safety criteria involve throwing errors over segfaults ?

@piv199
Copy link
Collaborator

piv199 commented Feb 5, 2017

@Khalian the same behaviour as get(at:)

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

No branches or pull requests
3 participants
@Khalian @Esqarrouth @piv199