<FromGitter>
<mixflame> yeah that's the one I'm using
<FromGitter>
<mixflame> in swift I had to import libsodium, there's swift code that goes along with my crystal code
<FromGitter>
<mixflame> swift client crystal server
<FromGitter>
<naqvis> for swift I believe there also exists crypto (swift implemented) library
<FromGitter>
<mixflame> yeah cryptokit. I used it already in my app. but I've never seen anyone recommending to mix crypto libraries and I failed when I tried on something as simple as SSL
<FromGitter>
<mixflame> swift also has swift-sodium though
<FromGitter>
<naqvis> that's interesting, it shouldn't be the case
<FromGitter>
<naqvis> because libraries implement the standard crypto algos
<FromGitter>
<naqvis> might be some variations in standards each library implements?
<FromGitter>
<mixflame> with SSL it was protocol version issues and socket bugs
<FromGitter>
<mixflame> maybe I can use crypto kit with sodium.cr tho... there's just no examples of that and the libraries work differently
<FromGitter>
<naqvis> worth trying
sagax has joined #crystal-lang
<FromGitter>
<drosehn> Anyone happen to know how to get the name of the current method as a string? Ruby has `__method__`, but crystal doesn't recognize that. I'm thinking it would be some macro call, but haven't found anything in a quick skimming of the documentation.