On Mon, Jul 8, 2013 at 2:00 AM, bearophile wrote:
> JS:
>
>
> I think when the code is compiled a "report" can be generated listing the
>> priorities along with the locations in the file would be beneficial...
>>
>
> It looks like a useful thing, on the other hand I think most people solve
> thi
JS:
I think when the code is compiled a "report" can be generated
listing the priorities along with the locations in the file
would be beneficial...
It looks like a useful thing, on the other hand I think most
people solve this with their IDEs instead of modifying the source
code.
Anyth
Is there an easy way to document future implementation details,
bugs, and modifications to code? I'm not too familiar with ddoc
and while it can be done I'm interested in a clean and direct way
to do this:
doc!("remove any gc dependence", 3);
doc!("fix bug #2345", 1);
void func() {}
where doc