Hecate2
Hecate2
The workaround is to ``` (ByteString)new byte[] { 0x9e, 0x09, 0x23, 0xa3, 0x9f, 0x51, 0x5e, 0x9a, 0x8c, 0xeb, 0xc9, 0xfb, 0x69, 0x4b, 0x9a, 0xbf, 0x7e, 0x4b, 0x8c, 0x3f, 0x7a, 0xb6,...
[HashedName.zip](https://github.com/neo-project/neo-devpack-dotnet/files/12746842/HashedName.zip) For the zip file of contract above, we can set a breakpoint at https://github.com/neo-project/neo-devpack-dotnet/blob/a77456b47636acfebe1fc78cad57f6ebfdc60109/src/Neo.Compiler.CSharp/MethodConvert.cs#L1234 and see that `constant.Value` is ``` "\u009e\t#£\u009fQ^\u009a\u008cëÉûiK\u009a¿~K\u008c?z¶ø\u001bV꽬PK\bÜ" ``` while `syntax` is ``` "\x9e\x09\x23\xa3\x9f\x51\x5e\x9a\x8c\xeb\xc9\xfb\x69\x4b\x9a\xbf\x7e\x4b\x8c\x3f\x7a\xb6\xf8\x1b\x56\xea\xbd\xac\x50\x4b\x08\xdc" ``` Then...
I think the compiler is OK, because it is always just an INITSLOT for the start of a method.
```csharp using System.ComponentModel; using Neo.SmartContract.Framework; using Neo.SmartContract.Framework.Attributes; using Neo.SmartContract.Framework.Services; namespace BigIntegerTest { [DisplayName("BigIntegerTest")] [ManifestExtra("Author", "Hecate2")] [ManifestExtra("Email", "[email protected]")] [ManifestExtra("Description", "ByteString comparison")] public class BigIntegerTest : SmartContract { public static void _deploy(object...
> How are you calling the method? In `RPC? Yes, in neo-fairy-client.
In our contract example, we never defined any BigInteger, and it should be quite OK to compare two ByteStrings. Maybe we can add a method in the RPC and neo-cli...
Tools -> Editor Options -> New Document Encoding: UTF-8. And make sure the opened file is also using UTF-8.
Tools -> Editor Options -> New Document Encoding: UTF-8. And make sure the opened file is also using UTF-8.
> Do any wallets even support divisible NFTs? No
My worship! My sage!