Timothee Cour

no context shown on DProtoSyntaxException => should show line number

3

@msoucy I have a large proto file, and get this error: ``` ~/.dub/packages/dproto-2.1.1/dproto/import/dproto/parse.d(511,11): Error: uncaught CTFE exception dproto.exception.DProtoSyntaxException("Expected an integer but was ``") ``` it should show offending line number...

is there an equivalent of MergeFrom in dproto?

3

https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.message if not, could that be on the roadmap? for reference: see also https://github.com/google/protobuf/issues/3106#issuecomment-302232227

fully qualified name from a proto?

1

@msoucy ``` mixin ProtocolBufferFromString!" package foo.bar; message Person {...} "; void test(){ static assert(Person.fqname=="foo.bar.Person"); } ``` is there anything similar to fqname? (static method returning at compile time the fully...

option to convert from a D struct to/from a Proto when this makes sense

2

would be nice to support conversions, when possible: eg: ``` d Person1 proto; Person2 s; proto.deserialize("..."); s.readFrom(proto); Person1 proto2; proto2.readFrom(s); assert(proto2==proto); ``` ``` proto message Person1 { required string name...

would be nice to show examples derived from real use cases

4

would be nice to show examples derived from real use cases to see where it works and where it doesn't yet work; eg with no imports: https://github.com/BVLC/caffe/blob/master/src/caffe/proto/caffe.proto more complex eg...

integrate/port/document find_libpython to find libpython for pyInitLibPath automatically

2

it's surprisingly hard to find libpython in a robust way; this does the trick but relies on an external python package `find_libpython`: ``` # ubuntu: $ pip3 install find_libpython $...

I'm on OSX. ``` Testing Python executable: python2 Testing Python executable: python3 Testing Python executable: python2 Traceback (most recent call last): File "tests/tnimfrompy.py", line 128, in s.testPyFromNim() nimpy.Exception: Unexpected error...

nimsuggest SIGSEGV when passing some unknown files

8

/cc @Araq now that https://github.com/nim-lang/Nim/pull/9757 was merged, the caveats I had mentioned in that PR hold: nimsuggest --stdin /Users/timothee/git_clone/nim/Nim/lib/system.nim def /Users/timothee/git_clone/nim/Nim/lib/system.nim:106:22 def /Users/timothee/git_clone/nim/Nim/compiler/modules.nim:69:63 gives SIGSEGV see stacktrace here: https://github.com/nim-lang/Nim/pull/9715#issuecomment-438935200

add debugging instructions

1

/cc @Araq I was trying to debug https://github.com/nim-lang/nimsuggest/issues/93 but ran into a number of issues; it turns out debugging nimsuggest is tricky, we should add instructions in `doc/nimsuggest.rst` * compiling...