Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unified Input/Output Rules

See original GitHub issue

Right now Surya has some mixed input/output rules. I propose unifying them to a common format.

For output, I suggest sending everything to stdout. For input, we should extend the rules Surya already has. Here is the current output from surya --help:

surya <cmd> [args]

  surya describe <files..>                  show file contracts structure.
  surya graph <files..>                     generate graph of contract function
  surya inheritance <files..>               generate graph of contract
                                            inheritance tree.
  surya dependencies <target_contract>      output a linearized list of smart
  <files..>                                 contract dependencies (linerized
                                            inherited parents).
  surya parse <file>                        output AST generated by the parser
                                            for the specified file in a textual
                                            tree format.
  surya ftrace <function_identifier>        output the selected function call
  <function_visibility_restrictor>          trace in a textual tree format.
  <files..>                                 External calls are marked in
                                            `orange` and internal calls are
  surya mdreport <outfile> <infiles..>      output a markdown file

  -h, --help     Show help                                             [boolean]
  -v, --version  Show version number                                   [boolean]

For a new format I would suggest we use the following convention across all of Surya’s operations input surya <cmd> infile1.sol infile2.sol ...

output stdout

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:5

github_iconTop GitHub Comments

GNSPScommented, Dec 4, 2018

But then in the dependencies command we should at least have an option to enable to target a single contract necasuse that’s the most usual use case.

chronaeoncommented, Dec 8, 2018



Read more comments on GitHub >

github_iconTop Results From Across the Web

Establish and maintain an input requirements definition ...
The data input management rules must include a data verificat… ... Supplementary Edition to other standards); approaches for secure input/output handling.
Read more >
The Online Method of Input/Output Unified GAS Reciprocating ...
The Online Method of Input/Output Unified GAS Reciprocating Generation Unit in Island Mode.
Read more >
Unified learning rules based on different cost functions
Citation: Szu HH, Ho P, Sun Y. Unified learning rules based on different cost ... Two neuronal input/output (I/O) states must be normalization...
Read more >
A unified input-output analysis of four-bar linkages
Proposed in this paper is a unified, robust algorithm for the input–output analysis of planar, spherical and spatial four-bar linkages.
Read more >
Logarithmic and Power Law Input-Output Relations in Sensory ...
Two central biophysical laws describe sensory responses to input signals. One is a logarithmic relationship between input and output, ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found