Bogdan Gusiev

The message is not hidden, you need to scroll right to see it. My point is that printing the entire source file to console when encountering an error is not...

Based on my research `UIImage` can contain the metadata so there is no need for additional object and API change. The metadata is lost somewhere during these transformations: ``` swift...

@FulcrumOne I researched it a little more and found that `UIImage` wrapper kills metadata: whatever you put to the constructor of `UIImage` can have a metadata, but after a call...

@samdogg7 I am already using this patch in production 👍 . Works well so far. Unfortunately, @FulcrumOne doesn't pay much attention to the repo and I have no power here....

> Getting the library version is even harder as there is no static way to get this information without evaluating code. I saw this fragment here and thought it is...

It can be related to https://github.com/twbs/bootstrap-rubygem/issues/288, however the broader issue is described there like inability to use bootstrap themes out of the box.

Yes, it looks like it breaks something. While I was investigating, I found that `solc` allows json output. I believe that would be far better solution than trying to part...

@rymdbar here is the problem: https://github.com/argotorg/solidity/issues/16107. I am open for advice on how to solve it without the patch to solidity itself.

Throwing an error with all parsed data is better. I think current IOError is too basic. JS libs work this way.

This is good step forward, but the error could be parsed better. The custom solidity errors are parsed the same way as events. They have parameters and those parameters have...