Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login
user: ealhad (* users last updated on 10/04/2024)
submissions comments favorites similar users
created: 2017-05-30 07:23:35
karma: 623
count: 193
Avg. karma: 3.23
Comment count: 188
Submission count: 5
Submission Points: 365
about: Free Software enthusiast

Haskell, Rust, Lisp(s)... and JavaScript.



user: EugeneOZ (* users last updated on 10/04/2024)
submissions comments favorites similar users
created: 2012-03-21 15:44:18
karma: 2439
count: 2014
Avg. karma: 1.21
Comment count: 1951
Submission count: 63
Submission Points: 767
about: https://jamm.dev

https://twitter.com/eugeniyoz

https://www.upwork.com/users/~01d95397aacaef6e88

http://careers.stackoverflow.com/oz

https://www.linkedin.com/in/newmanoz/




You need an encrypted connection, period.

If you only use an encrypted connection when you need it, then one can know that, well, you need it.

You have nothing to hide... until you do.


Connection is encrypted

As I pointed in my reply, you could also try KeePass Touch.

Try KeePass.

This looks really neat, I played with it a bit and the DSL is well thought out.

One thing I can't figure though: how do we set default values for internal Struct?

Said default values are mentionned in the documentation (here: <https://slint.dev/releases/1.0.2/docs/slint/src/reference/ty...>).

  // ok even if a is missing, it will just have the default value

> Implement Default then call it

It's far from "default values in struct declaration". I mean this:

struct X { i:u32 = 5, j:u64 }


Legal | privacy