import: import log crate as baseline

[pawelrutkaq]

Import from log crate 3aa1359e926a39f841791207d6e57e00da3e68e2 at https://github.com/rust-lang/log

This is as follow up to decision in CFG Logging: eclipse-score/inc_mw_log#6 (comment)
to enable Rust code with common frontend.

Please consider that this is only enabler (eclipse-score/inc_mw_log#5), and frontend will be done from scratch in S-CORE (however it will be macro compatible). The Rust binding to C++ mw::log will be located in new logging repo.

[pawelrutkaq]

@hoppe-and-dreams @rmaddikery @arsibo The frontend was moved as requested. (FYI: @darkwisebear )

[FScholPer]

Can you please first request the upstream to change if that doesn't work we should to a real fork in a separate repository.

[pawelrutkaq]

Can you please first request the upstream to change if that doesn't work we should to a real fork in a separate repository.
Not sure what does not work ?:)

[rmaddikery]

Since the repo does not have all the checks in place please add in description if you follow Rust's naming convention and coding guidelines? E.g.: https://github.com/rust-lang/style-team/blob/master/guide/guide.md

I see few unit tests, but not covered for all. Is this planned?
https://doc.rust-lang.org/rust-by-example/testing.html

[pawelrutkaq]

Follow ups plannned after this PR:
eclipse-score/score#1896
eclipse-score/score#1897

For "imported" code, this is as is. As in above, this going to be fixed in MVP

[rmaddikery]

A readme can be useful that demonstrates the usage and assumptions of use

[pawelrutkaq]

Since the repo does not have all the checks in place please add in description if you follow Rust's naming convention and coding guidelines? E.g.: https://github.com/rust-lang/style-team/blob/master/guide/guide.md

I see few unit tests, but not covered for all. Is this planned? https://doc.rust-lang.org/rust-by-example/testing.html

As this is enabler from open source, no UT planned for this code. Only for new MVP providing proper frontend.

[rmaddikery]

IS this missing?

[pawelrutkaq]

Done

[pawelrutkaq]

Since the repo does not have all the checks in place please add in description if you follow Rust's naming convention and coding guidelines? E.g.: https://github.com/rust-lang/style-team/blob/master/guide/guide.md

I see few unit tests, but not covered for all. Is this planned? https://doc.rust-lang.org/rust-by-example/testing.html

Quality and naming output:
pawel@pawel-VirtualBox ~/qorix/repos/baselibs/score/mw/log/rust (pawelrutkaq_rust_log_frontend) $ cargo clippy
Checking mw_log v0.0.1 (/home/pawel/qorix/repos/baselibs/score/mw/log/rust)
Finished dev profile [unoptimized + debuginfo] target(s) in 0.15s

pawel@pawel-VirtualBox ~/qorix/repos/baselibs/score/mw/log/rust (pawelrutkaq_rust_log_frontend) $ cargo build
Compiling mw_log v0.0.1 (/home/pawel/qorix/repos/baselibs/score/mw/log/rust)
Finished dev profile [unoptimized + debuginfo] target(s) in 0.11s

So common pratices for Rust followed.

[pawelrutkaq]

@darkwisebear @4og @arsibo This is now done the way we agreed on (https://github.com/orgs/eclipse-score/discussions/236#discussioncomment-14759725). Can we have last look and continue ?

[pawelrutkaq]

Managed to release score-crates so updated deps.

[4og]

Hi @pawelrutkaq, your change is merged in 8e017e0 and 64924b7. Thank you for contribution!