An error in record.rs in core
XieLeii opened this issue · 2 comments
How should I solve it? If you can help me, I will be very grateful
Here are the details:
Compiling seq_io v0.4.0-alpha.0 (https://github.com/markschl/seq_io#3d461a36)
error: unexpected token
--> .cargo/git/checkouts/seq_io-5c12caa4159d1858/3d461a3/src/core/record.rs:21:19
|
21 | concat!("use seq_io::", $module_path, "::{Reader, RecordSet};"),
| ^
|
::: /home/xl/.cargo/git/checkouts/seq_io-5c12caa4159d1858/3d461a3/src/fastx/record.rs:454:1
|
454 | impl_recordset!(RefRecord, QualRecordPosition, LineStore, "fastx", "fastq");
| --------------------------------------------------------------------------- in this macro invocation
|
= note: this error originates in the macro impl_recordset
(in Nightly builds, run with -Z macro-backtrace for more info)
error: unexpected token
--> /home/xl/.cargo/git/checkouts/seq_io-5c12caa4159d1858/3d461a3/src/core/record.rs:21:19
|
21 | concat!("use seq_io::", $module_path, "::{Reader, RecordSet};"),
| ^
|
::: /home/xl/.cargo/git/checkouts/seq_io-5c12caa4159d1858/3d461a3/src/fasta/record.rs:269:1
|
269 | impl_recordset!(RefRecord, SeqRecordPosition, LineStore, "fasta", "fasta");
| -------------------------------------------------------------------------- in this macro invocation
|
= note: this error originates in the macro impl_recordset
(in Nightly builds, run with -Z macro-backtrace for more info)
error: unexpected token
--> /home/xl/.cargo/git/checkouts/seq_io-5c12caa4159d1858/3d461a3/src/core/record.rs:21:19
|
21 | concat!("use seq_io::", $module_path, "::{Reader, RecordSet};"),
| ^
|
::: /home/xl/.cargo/git/checkouts/seq_io-5c12caa4159d1858/3d461a3/src/fastq/record.rs:361:1
|
361 | impl_recordset!(RefRecord, QualRecordPosition, RangeStore, "fastq", "fastq");
| ---------------------------------------------------------------------------- in this macro invocation
|
= note: this error originates in the macro impl_recordset
(in Nightly builds, run with -Z macro-backtrace for more info)
Thanks for letting me know about this problem. Unfortunately I'm still working on a second alpha version, which turned out to be again almost a complete rewrite (see also #9). Therefore I won't fix anything in v0.4.0-alpha.0. I'm still in the phase of getting the code actually working and I don't feel comfortable yet with pushing anything to GitHub.
For now, I recommend to use version v0.3.1. If you need a special feature from v0.4.0-alpha.0, I can only suggest to wait (maybe tell me what you need to make sure that I have it in the next alpha), or implement it yourself for 0.3.x and issue a PR.
ok, thank you!