Pool: claiming to the pool itself causes accounting issues
```\\nfunction \\_claim(address from, address to) internal returns (uint256) {\\n    (uint256 amountReward, uint256 amountPool) = redeemableReward(from);\\n    require(amountPool != 0, "Pool: User has no redeemable pool tokens");\\n\\n    \\_burnFrom(from, amountPool);\\n    \\_incrementClaimed(amountReward);\\n\\n    rewardToken.transfer(to, amountReward);\\n    return amountReward;\\n}\\n```\\n\\nIf the destination address `to` is the pool itself, the pool will burn tokens and increment the amount of tokens claimed, then transfer the reward tokens `to` itself.
Resolution\\nThis was addressed in fei-protocol/fei-protocol-core#57\\nPrevent claims from specifying the pool as a destination.
```\\nfunction \\_claim(address from, address to) internal returns (uint256) {\\n    (uint256 amountReward, uint256 amountPool) = redeemableReward(from);\\n    require(amountPool != 0, "Pool: User has no redeemable pool tokens");\\n\\n    \\_burnFrom(from, amountPool);\\n    \\_incrementClaimed(amountReward);\\n\\n    rewardToken.transfer(to, amountReward);\\n    return amountReward;\\n}\\n```\\n