Unlike c++, in #rust, function and struct declaration order does not matter.
What is the best practice then? From lower-level (no deps) to higher-level (all deps) like in c++? Or the reverse so that you start reading a file from the higher level code? #asknostr #devstr
sommerfeld
npub16r…kz5pl
2024-06-27 10:16:32
Author Public Key
npub16r0tl8a39hhcrapa03559xahsjqj4s0y6t2n5gpdk64v06jtgekqdkz5plPublished at
2024-06-27 10:16:32Event JSON
{
"id": "b932d5f007f0cad98e984215f4ce5e9e961d7692faeacb2c5b04c136c242ebb0",
"pubkey": "d0debf9fb12def81f43d7c69429bb784812ac1e4d2d53a202db6aac7ea4b466c",
"created_at": 1719483392,
"kind": 1,
"tags": [
[
"t",
"rust"
],
[
"t",
"asknostr"
],
[
"t",
"devstr"
]
],
"content": "Unlike c++, in #rust, function and struct declaration order does not matter.\nWhat is the best practice then? From lower-level (no deps) to higher-level (all deps) like in c++? Or the reverse so that you start reading a file from the higher level code? #asknostr #devstr",
"sig": "4ccf0bcc544d09fc8026d1ba7ad0d3a5b2a2871dcbf7a82dbe9138efd60e4453513ed847dd58b96ace5a5fdd7ef8160881eac75b508b2faf8b4e9b9c53f2ad95"
}