考虑以下示例信托项目:
.
├── contracts
│ ├── Foo.sol
│ └── Migrations.sol
├── migrations
│ ├── 1_initial_migration.js
│ └── 2_foo.js
├── test
│ └── Foo.test.js
└── truffle.jscontracts/Foo.sol的内容:
pragma solidity ^0.4.21;
contract Foo {
enum Bar {zero, one, two, three}
function getOne() public pure returns (Bar) {
return Bar.one;
}
}test/Foo.test.js的内容:
let Foo = artifacts.require("./Foo.sol");
contract("", async (accounts) => {
it("", async () => {
let instance = await Foo.deployed();
let one = await instance.getOne();
assert.equal(one, 1);
});
});让我们测试我们的项目:
$ truffle test
Compiling ./contracts/Foo.sol...
Compiling ./contracts/Migrations.sol...
Contract:
✓
1 passing (27ms)如你所见,一切都很完美。现在,为了科学起见,让我们将合同转换为contracts/Foo.sol中的一个库:
pragma solidity ^0.4.21;
library Foo {
enum Bar {zero, one, two, three}
function getOne() public pure returns (Bar) {
return Bar.one;
}
}让我们再做一次测试:
$ truffle test
Compiling ./contracts/Foo.sol...
Compiling ./contracts/Migrations.sol...
Contract:
1)
> No events were emitted
0 passing (32ms)
1 failing
1) Contract: :
Error: invalid solidity type!: Foo.Bar
at SolidityCoder._requireType (/home/emilio/.nvm/versions/node/v9.8.0/lib/node_modules/truffle/build/webpack:/~/web3/lib/solidity/coder.js:61:1)
at /home/emilio/.nvm/versions/node/v9.8.0/lib/node_modules/truffle/build/webpack:/~/web3/lib/solidity/coder.js:231:1
at Array.map ()
at SolidityCoder.getSolidityTypes (/home/emilio/.nvm/versions/node/v9.8.0/lib/node_modules/truffle/build/webpack:/~/web3/lib/solidity/coder.js:230:1)
at SolidityCoder.decodeParams (/home/emilio/.nvm/versions/node/v9.8.0/lib/node_modules/truffle/build/webpack:/~/web3/lib/solidity/coder.js:203:1)
at SolidityFunction.unpackOutput (/home/emilio/.nvm/versions/node/v9.8.0/lib/node_modules/truffle/build/webpack:/~/web3/lib/web3/function.js:113:1)
at Object.callback (/home/emilio/.nvm/versions/node/v9.8.0/lib/node_modules/truffle/build/webpack:/~/web3/lib/web3/function.js:145:1)
at /home/emilio/.nvm/versions/node/v9.8.0/lib/node_modules/truffle/build/webpack:/~/web3/lib/web3/method.js:142:1
at /home/emilio/.nvm/versions/node/v9.8.0/lib/node_modules/truffle/build/webpack:/~/web3/lib/web3/requestmanager.js:89:1
at /home/emilio/.nvm/versions/node/v9.8.0/lib/node_modules/truffle/build/webpack:/~/truffle-provider/wrapper.js:134:1
at XMLHttpRequest.request.onreadystatechange (/home/emilio/.nvm/versions/node/v9.8.0/lib/node_modules/truffle/build/webpack:/~/web3/lib/web3/httpprovider.js:128:1)
at XMLHttpRequestEventTarget.dispatchEvent (/home/emilio/.nvm/versions/node/v9.8.0/lib/node_modules/truffle/build/webpack:/~/xhr2/lib/xhr2.js:64:1)
at XMLHttpRequest._setReadyState (/home/emilio/.nvm/versions/node/v9.8.0/lib/node_modules/truffle/build/webpack:/~/xhr2/lib/xhr2.js:354:1)
at XMLHttpRequest._onHttpResponseEnd (/home/emilio/.nvm/versions/node/v9.8.0/lib/node_modules/truffle/build/webpack:/~/xhr2/lib/xhr2.js:509:1)
at IncomingMessage. (/home/emilio/.nvm/versions/node/v9.8.0/lib/node_modules/truffle/build/webpack:/~/xhr2/lib/xhr2.js:469:1)
at endReadableNT (_stream_readable.js:1101:12)
at process._tickCallback (internal/process/next_tick.js:114:19)为什么?
首先,我对自己说:当然,这是因为库不能有状态变量。但后来我意识到enum不是一个状态变量;它是一个类型定义。我想说,使用 structs的文档在本质上类似于enums。此外,尽管在这个例子中没有显示出来,但当引用合同中的图书馆枚举时,它编译得很好,这可能意味着这是一个web3js问题。
那怎么回事?这是故意的吗?这里的最佳做法是什么?在每个使用库的合同中定义enum?把enum变成struct?我遗漏了什么?
Reproducibility信息
为了重现性,我包含了migrations/2_foo.js的(相当琐碎的)内容:
let Foo = artifacts.require("./Foo.sol");
module.exports = (deployer) => {
deployer.deploy(Foo);
};和truffle.js:
module.exports = {
networks: {
development: {
host: "127.0.0.1",
port: 8545,
network_id: "*" // Match any network id
}
}
};如您所知,其余的文件是由truffle init创建的。
我还在一个单独的终端上运行ganache-cli,作为我的测试网。
下面是我使用的开发工具的版本:
$ truffle version
Truffle v4.1.5 (core: 4.1.5)
Solidity v0.4.21 (solc-js)
$ ganache-cli version
Ganache CLI v6.1.0 (ganache-core: 2.1.0)发布于 2018-04-12 15:23:32
如果将其转换为整数类型,则它将正常工作。
function getOne() public pure returns (uint) {
return uint(Bar.one);
}我不知道为什么如果没有明确的铸造它就不能工作。这是另一个有用的例子,但需要一个合同。
pragma solidity 0.4.21;
library Foo {
enum Bar {zero, one, two, three}
function getOne() public pure returns (Bar) {
return Bar.one;
}
}
contract Bar {
function getOne() public pure returns(Foo.Bar) {
return Foo.getOne();
}
}编辑:
这是对坚实性文件的评论。
// Since enum types are not part of the ABI, the signature of "getChoice"
// will automatically be changed to "getChoice() returns (uint8)"
// for all matters external to Solidity. The integer type used is just
// large enough to hold all enum values, i.e. if you have more values,
// `uint16` will be used and so on.不知为何,当为库创建ABI时,错误地生成了:
"abi": [
{
"constant": true,
"inputs": [],
"name": "getOne",
"outputs": [
{
"name": "",
"type": "Foo.Bar"
}
],
"payable": false,
"stateMutability": "pure",
"type": "function"
}
],虽然它是为合同创建的,但它工作得很好:
"abi": [
{
"constant": true,
"inputs": [],
"name": "getOne",
"outputs": [
{
"name": "",
"type": "uint8"
}
],
"payable": false,
"stateMutability": "pure",
"type": "function"
}
],所以我可能会说它看起来像编译器的一个bug,或者是像这样的设计,我不能回答这个问题。但是,由于库用于内部调用--而不是外部调用--它可能是一种设计选择。
不管怎么说,我的建议是用合同来履行这种要求。您可能有需要存储的函数,而访问它的唯一方法是使用契约。库对于重用代码和跨契约执行公共任务非常有用。
https://ethereum.stackexchange.com/questions/45486
复制相似问题