Live data from Hacker News

Viewing profile — Pharohbot

Pharohbot

HN member
Joined
Fri, Oct 17, 2014, 10:34 PM UTC
HN karma
209
Public activity
85 items

About Pharohbot

No profile information was provided.

Recent public activity

  1. story
  2. comment
    Comment #9678112

    Well if you have decent tools to debug them, why should he be wary?

  3. comment
    Comment #9671018

    Well the biggest concern for most is null pointers, so invoking not nil on the pointers would suffice for most

  4. story
  5. comment
    Comment #9649737

    when --nilChecks:On become a thing, dereferencing null pointers will be like Java, a NilError (NullPointerException in Java). This is why I said it's as safe mainstream languages t…

  6. comment
    Comment #9649722

    Since when were we comparing Nim and Rust? yes Rust is more safe than Nim, but that comes with tradeoffs. You are obviously not reading the whole thread about me bringing up (multi…

  7. comment
    Comment #9649708

    > Because it isn't true Did you not see the other person who just said that? > Strawman ... the comment was about scripting languages. I do not have a clue what you are trying to s…

  8. comment
    Comment #9644986

    I never said that Nim is safe/ doesnt have safe areas in the language. But at this stage of development with Nim, it really focuses on the Language goals rather than anything else …

  9. comment
  10. comment
  11. comment
  12. comment
    Comment #9644970

    As stated before in this thread, there _will_ be nil Checks in the future which will result in NilErrors or you can just annotate it with `not nil` right now and it will never be n…

  13. comment
    Comment #9643384

    I probably should have been more clear, but I think it's safe to say that unlike C/C++, Nim can handle these types of issues like other languages that deal with pointers (Java, Go …

  14. comment
    Comment #9643372

    It really depends on how you define "safe". Nim will allow you to deref null pointers (unless you annotate it with `not nil`, then it can never be nil, this results in compile erro…

  15. comment
    Comment #9643117

    As stated before, there are ways to avoid them and ways that Nim will soon handle them, but do you know how many other languages deref a NULL pointer? Unlike C, this does not resul…

  16. comment
    Comment #9642681

    Uhh that's not much of an answer...

  17. comment
    Comment #9642680

    Yes Rust is more safe than Nim, I'm not arguing that. I'm also not arguing that Nim is as safe as languages with automatic memory management. EDIT: Also, Nim is planning on turning…

  18. comment
    Comment #9642495

    Do you have any specific examples of these unsafetiness in Nim?

  19. comment
    Comment #9642397

    Why not? I'm interested to know because in my opinion I don't see it any less safe than languages that don't have automatic memory management and/or languages like Rust.

  20. comment
    Comment #9642146

    Nim is as safe as any other language. Perhaps it's not as safe as Rust but that brings specific trade offs most people dont wan't to deal with. I don't understand why people think …

  21. comment
    Comment #9641581

    A more general approach to shared memory via lockable heaps is a feature Nim seems will implement soon.

  22. story
  23. story
  24. comment
  25. story