
V Sun, 5 Jan 2020 11:51:29 +0100 Ancor Gonzalez Sosa <ancor@suse.de> napsáno:
On 1/3/20 12:24 PM, Ancor Gonzalez Sosa wrote:
On 1/3/20 11:31 AM, Josef Reidinger wrote:
V Fri, 3 Jan 2020 11:14:15 +0100
Hi, this is quite interesting. Especially similarities in testing looks nice. I have few questions:
I have to say that my feeling is that similarities in testing are not as deep as they may look in the surface. Tests in Crystal use almost exactly the same syntax that RSpec, but AFAIK there is nothing like "let" and nothing like rspec-mocks.
Good news, I added Spectator[1] to the project and now both test files disk_size_test.rb and disk_size_spec.cr are basically identical.
The Spectator home page claims that "developers coming from Ruby and RSpec will feel right at home" and I must say it's absolutely true.
Cheers.
Good to heard that. Then maybe we can try for some serious usage took the most compute intensive part of yast2-storage-ng ( I think computing proposal is the winner now, not? ) and try to write it in crystal. When I think about it, it probably need two input - current state + configuration ( defaults + product specific changes + maybe user changes from guided setup integrated together? ) and return the proposed action to apply on graph ( or target graph, but I worry it cannot be easily import to libstorage-ng ). And when we have it compare speed. I think the task is good also because it can be well paralleled and we already reach its limit in some bug reports. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org