-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Conversation
@@ -642,37 +629,14 @@ impl<C, SN: ?Sized, S: ?Sized, M, EM> Eth for EthClient<C, SN, S, M, EM> where | |||
} | |||
|
|||
fn compile_lll(&self, _: String) -> Result<Bytes, Error> { | |||
rpc_unimplemented!() | |||
Err(errors::deprecated("Compilation of LLL via RPC is deprecated".to_string())) | |||
} | |||
|
|||
fn compile_serpent(&self, _: String) -> Result<Bytes, Error> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When deprecating RPC methods, marking them as @deprecated
in the trait definition will help us keep the wiki in sync, since the markdown builder checks for those. Example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, wasn't aware of this feature.
looks like they've been more than deprecated - they've been removed... |
Yep, those RPC calls are not used by the UI |
Yes, I think it makes sense to remove them. Only solidity compilation was ever supported, and then only if Honestly, nobody uses these RPCs for a wide variety of reasons, and those who do would almost certainly be more productive with real development tools. |
See ethereum/EIPs#209
We don't use this in the UI AFAIK, the contract editor just uses browser-solidity, right @ngotchac?