Hello community, how are you all doing? My name is Sebastian, I'm 23 years old and I'm from Santiago
I don't have any professional qualifications in computer science or informatics but I studied electronics and have a strong foundation in various basic concepts and tools/languages
Today I'm writing to ask you all for learning resources. I'm looking to learn and practice Ruby and all its different aspects, from the very basics up to writing professional level code.
I want to learn best practices from the start, so that no matter what the current level I'm on my learning curve, I can write code using the latest advances and techniques, so that whatever I'm programming is done in the most professional and efficient way possible.
I don't have a lot of expertise but I'm looking to start my journey with a solid foundation, and I decided to write this to the most appropriate group of people.
Greetings from Chile!
flog version 4.7.0 has been released!
* home: <http://ruby.sadi.st/>
* code: <https://github.com/seattlerb/flog>
* rdoc: <http://docs.seattlerb.org/flog>
* vim: <http://github.com/sentientmonkey/vim-flog>
Flog reports the most tortured code in an easy to read pain
report. The higher the score, the more pain the code is in.
Changes:
### 4.7.0 / 2023-07-18
* 3 minor enhancements:
* Extend flog to process complex numbers. (petergoldstein)
* Only penalize magic numbers if they're not assigned to a const (excludes 0/-1).
* Renamed :lit_fixnum to :magic_number.
Ich kehre zurück am 29.07.2023.
Sehr geerhte Damen und Herren!
Ich bin von 13.07.2023 bis 29.07.2023 auf Urlaub und habe nicht immer die
Möglichkeit meine Mails zu lesen!
Ich werde diese aber so schnell als möglich beantworten!
Mit freundlichen Grüßen
Jörg Meidl
Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht
"[ruby-talk:444277] [ANN] glimmer-dsl-swt 4.28.0.0 Released"( gesendet am
14.07.2023 22:30:26) .
Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während
diese Person abwesend ist.
Dear Ruby Mailing List,
Is there a way to do data driven testing with minitest? I am stuck on a
kata I'm working on that may benefit from this, and would appreciate
resources on this.
Yours sincerely,
Hemal
--
"Musbury",
16 Devonshire Road,
Mill Hill,
London,
NW7 1LL
Home: +44 (0) 208 346 6444
Mobile: +44 (0) 7751 879 908
ruby_parser version 3.20.3 has been released!
* home: <https://github.com/seattlerb/ruby_parser>
* bugs: <https://github.com/seattlerb/ruby_parser/issues>
* rdoc: <http://docs.seattlerb.org/ruby_parser>
ruby_parser (RP) is a ruby parser written in pure ruby (utilizing
racc--which does by default use a C extension). It outputs
s-expressions which can be manipulated and converted back to ruby via
the ruby2ruby gem.
As an example:
def conditional1 arg1
return 1 if arg1 == 0
return 0
end
becomes:
s(:defn, :conditional1, s(:args, :arg1),
s(:if,
s(:call, s(:lvar, :arg1), :==, s(:lit, 0)),
s(:return, s(:lit, 1)),
nil),
s(:return, s(:lit, 0)))
Tested against 801,039 files from the latest of all rubygems (as of 2013-05):
* 1.8 parser is at 99.9739% accuracy, 3.651 sigma
* 1.9 parser is at 99.9940% accuracy, 4.013 sigma
* 2.0 parser is at 99.9939% accuracy, 4.008 sigma
* 2.6 parser is at 99.9972% accuracy, 4.191 sigma
* 3.0 parser has a 100% parse rate.
* Tested against 2,672,412 unique ruby files across 167k gems.
* As do all the others now, basically.
Changes:
### 3.20.3 / 2023-07-11
* 2 minor enhancements:
* Added Parser#in_argdef and integrated into 3.x parsers.
* Improved tools/munge.rb to handler MRI 3.2 output
* 2 bug fixes:
* Fixed process_dots to properly deal with paren-less forward_args. (eric1234)
* Fixed tools/ripper.rb to properly print ripper sexp at the end
minitest-focus version 1.4.0 has been released!
* home: <https://github.com/seattlerb/minitest-focus>
* rdoc: <http://docs.seattlerb.org/minitest-focus>
Allows you to focus on a few tests with ease without having to use
command-line arguments. Good for tools like guard that don't have
enough brains to understand test output. Cf. minitest-autotest (an
example of a test runner with strong testing logic).
Inspired by https://github.com/seattlerb/minitest/issues/213
Changes:
### 1.4.0 / 2023-07-11
* 1 minor enhancement:
* Added --no-focus flag to disable focus and allow --name args to override.
Glimmer DSL for LibUI 0.0.8 has been released with a new feature called
Composite Shape (already in Glimmer DSL for SWT), which enables building
new visual concepts by aggregating multiple smaller shapes within a parent
composite shape using relative positioning and inherited `fill`/`stroke`
colors.
https://raw.githubusercontent.com/AndyObtiva/glimmer-dsl-libui/master/image…
Blog Post Announcement:
https://andymaleh.blogspot.com/2023/07/glimmer-dsl-for-libui-composite-shap…
GitHub: https://github.com/AndyObtiva/glimmer-dsl-libui
RubyGem: https://rubygems.org/gems/glimmer-dsl-libui
Change Log:
0.0.8:
- Support `composite_shape` keyword (alias: `shape`) as aggregate
(composite) shape that can have arbitrary shapes, text, transforms
underneath, which inherit its `fill`/`stroke` colors and `transform`.
`composite_shape` also supports nesting mouse listeners, which check mouse
click point containment against all nested shapes automatically.
- New `examples/basic_composite_shape.rb` with use of `shape` + drag and
drop support for moving shapes and click support for changing shape colors
- Invert `Glimmer::LibUI::ControlProxy::KEYWORD_ALIASES` to enable adding
multiple aliases per keyword
- Support `Glimmer::LibUI::Shape::KEYWORD_ALIASES` to enable adding
multiple aliases per keyword
- Small update for `examples/button_counter.rb`
minitest-bisect version 1.7.0 has been released!
* home: <https://github.com/seattlerb/minitest-bisect>
* rdoc: <http://docs.seattlerb.org/minitest-bisect>
Hunting down random test failures can be very very difficult,
sometimes impossible, but minitest-bisect makes it easy.
minitest-bisect helps you isolate and debug random test failures.
If your tests only fail randomly, you can reproduce the error
consistently by using `--seed <num>`, but what then? How do you figure
out which combination of tests out of hundreds are responsible for the
failure? You know which test is failing, but what others are causing
it to fail or were helping it succeed in a different order? That's
what minitest-bisect does best.
Changes:
### 1.7.0 / 2023-07-06
* 1 major enhancement:
* Extend bisect_methods to do "inverse" run (eg false positives) via -n=/RE/ argument.
* 4 minor enhancements:
* Added example_inverse.rb
* Collapsed examples from directories to individual files.
* Refactor: push command generation from #run down to #bisect_methods.
* build_files_cmd no longer calls reset (zero effect change).
* 4 bug fixes:
* 100% documentation coverage.
* Fix server process ID to be a string to match rest of args.
* Fix shebang cmd on bin/minitest_bisect.
* Print known bad methods with found culprit methods in final run.