"Ruby from Other Languages" > "To Ruby From C and C++"
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 944
- Forks
- 673
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 9
Description
Needs review and updating for new features since 2.0
page path:
"/documentation/ruby-from-other-languages/to-ruby-from-c-and-cpp/"
(1) section Similarities with C++
The C++ -> operator is mentioned. The new Ruby use of the -> operator for declaring Proc objects should perhaps be mentioned (in the Differences section, and linked from here.)
(2) section Differences from C++
"There’s only two container types:
ArrayandHash."
What of Set, Struct, Matrix or Range ?
(3) section Differences from C++
"There’s no type conversions. With Ruby though, you’ll probably find that they aren’t necessary."
Should there be mention of coercion ?
Or the global functions such as Integer(), Float(), etc.
(4) section Differences from C++
"Multithreading is built-in, but as of Ruby 1.8 they are “green threads” (implemented only within the interpreter) as opposed to native threads."
This appears to not have been changed since 1.8. Has this changed with 2.x and later ?
- All "Ruby from Other Languages" pages should be reviewed for changes since v 1.8.x.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with /documentation/ruby-from-other-languages/to-ruby-from-c-and-cpp/ and read the “Similarities with C++” and “Differences from C++” sections, including each quoted statement. Check the documented points about Proc syntax, container types, coercion and conversions, and threading against current Ruby behavior. Done means updating this page and reviewing the other “Ruby from Other Languages” pages for changes since Ruby 1.8.x.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100