qouteall

6 ms·

1. 31.▲
   by qouteall 11mo ago

   There is borgo https://github.com/borgo-lang/borgo but it's not yet mature and not being actively developed
2. 32.▲
   by qouteall 11mo ago

   For example , if error data contains string, if it directly point to input string it won't require allocation, but will have memory safety issue if error is passed to outer scope where input string is deallocated. Many errors copy stri
3. 33.▲
   by qouteall 11mo ago

   I agree that building a special diagnostic system is better than just using language's builtin error system. However that takes efforts. Library developers tend to choose the path of least resistance, which is to not pass diagnostic in
4. 34.▲
   by qouteall 11mo ago

   If the error rarely happens then passing error data shouldn't affect performance in visible way. If the error occurs in common path then it's designed wrongly. I agree that in special states like OOM passing error data with alloca
5. 35.▲
   by qouteall 11mo ago

   Changed to "valid reasons"
6. 36.▲
   by qouteall 11mo ago

   I know that Zig doesn't allow attaching data to error for valid reasons. If error data contains interior pointer then it can easily cause memory safety problem. Zig doesn't have a borrow cheker or ownership system to prevent that.
7. 37.▲
   by qouteall 11mo ago

   In my opinion the biggest issue of Zig is that it doesn't allow attaching data to error. The error can only be passed via side channel, which is inconvenient and ENOURAGES TOOL DEVELOPERS TO NOT PASS ERROR DATA, which greatly increase
8. 38.▲
   by qouteall 11mo ago

   Simplify: tokio::select! will discard other futures when one future progress. The discarded futures will never be run again. Normally when a future is discarded it's dropped. When a future holding lock is dropped, lock is released, but
9. 39.▲
   by qouteall 1y ago

   Thanks for suggestion.
10. 40.▲
    by qouteall 1y ago

    I added that into article
11. 41.▲
    by qouteall 1y ago

    I added clarification (That simplified example is just for illustrating contagious borrow issue. The *`total_score` is analogous to a complex state that exists in real applications*. Same for subsequent examples. Just summing integer can us
12. 42.▲
    Rust Contagious Borrow Issue(qouteall.fun)

    44 points by qouteall 1y ago|10 comments
13. 43.▲
    Higher-Level Design Patterns(qouteall.fun)

    1 points by qouteall 1y ago|0 comments
14. 44.▲
    How to avoid fighting the Rust borrow checker(qouteall.fun)

    26 points by qouteall 1y ago|9 comments
15. 45.▲
    by qouteall 1y ago

    In part 2 https://www.bitflux.ai/blog/memory-is-slow-part2/ the last diagram still shows that memory is faster than disk.
16. 46.▲
    How to Avoid Fighting Rust Borrow Checker(qouteall.fun)

    2 points by qouteall 1y ago|0 comments
17. 47.▲
    Concept Poisoning: Probing LLMs without probes(lesswrong.com)

    3 points by qouteall 1y ago|0 comments
18. 48.▲
    by qouteall 1y ago

    Thanks for your suggestions.
19. 49.▲
    by qouteall 1y ago

    Added
20. 50.▲
    by qouteall 1y ago

    Thanks for reminding. Added.
21. 51.▲
    by qouteall 1y ago

    updated
22. 52.▲
    by qouteall 1y ago

    Corrected.
23. 53.▲
    by qouteall 1y ago

    I changed the wording of it.
24. 54.▲
    by qouteall 1y ago

    Thanks I will correct that
25. 55.▲
    by qouteall 1y ago

    Thanks I will correct that
26. 56.▲
    by qouteall 1y ago

    Thanks I will correct that
27. 57.▲
    Traps to Developers(qouteall.fun)

    256 points by qouteall 1y ago|107 comments
28. 58.▲
    Weight sharing is the inverse of MoE(samsja.github.io)

    2 points by qouteall 2y ago|0 comments
29. 59.▲
    To create something new, you need to make some noise(ethansmith2000.com)

    2 points by qouteall 2y ago|0 comments
30. 60.▲
    by qouteall 2y ago

    For moving argument order and removing parameter is already doable by a mature IDE and they are more predictable than AI (Jetbrains IDEs support them well. In VSCode it may need extensions.) But adding parameter is not well supported by IDE