ci: coalesce styles

[tisonkun]

Comments inline.

cc @jeertmans

[codspeed-hq]

Merging this PR will not alter performance

✅ 6 untouched benchmarks

---

_{Comparing tisonkun:coalesce-ci (1ff0091) with master (1b23291)}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.09%. Comparing base (1b23291) to head (1ff0091).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #533   +/-   ##
=======================================
  Coverage   65.09%   65.09%           
=======================================
  Files          29       29           
  Lines        1825     1825           
=======================================
  Hits         1188     1188           
  Misses        637      637           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[tisonkun]

I'll next organize the tests and bences dirs better, and then start to improve the impl code.

Perhaps we can leverage some tech like serde_derive and serde_derive_internal to avoid one more dep level when they are actually shared code.

Besides, Logos provides several cool utility for debugging but they are not quite easy for discovering (graph printer, cli, etc.)

Before doing anything above, I typically tend to go through the repo setup so that developing in a well-formed structure rather than workaround any if I encount them later.

[jeertmans]

Hi @tisonkun, thanks for your contribution!

I'll next organize the tests and bences dirs better, and then start to improve the impl code.

Perhaps we can leverage some tech like serde_derive and serde_derive_internal to avoid one more dep level when they are actually shared code.

Besides, Logos provides several cool utility for debugging but they are not quite easy for discovering (graph printer, cli, etc.)

Before doing anything above, I typically tend to go through the repo setup so that developing in a well-formed structure rather than workaround any if I encount them later.

Do you plan to perform those changes here? Or in another PR?

[tisonkun]

@jeertmans thanks for your review!

I'd implement them one by one, not push everything in a big (mud) PR :D

[tisonkun]

That is, this PR is mergable and I'd prefer to contribute changes one by one to avoid rebase too many times :P

[jeertmans]

Sure! LGTM :-) Thanks!