Note that there are some explanatory texts on larger screens.

plurals
  1. POCan anyone else reproduce this bug in the Dart debugger/editor?
    primarykey
    data
    text
    <p>For my sanity, can someone verify a strange bug I'm having with the dart editor?</p> <p>I'm using the latest dart editor from the main page of the website, I downloaded, extracted, then ran the "DartEditor" executable. (I didn't clear any previous settings that were stored elsewhere, but I don't think that will change the issue.)</p> <pre><code>Dart Editor version 1.0.0_r30798 (STABLE) Dart SDK version 1.0.0.10_r30798 </code></pre> <ul> <li>Download my repository: <a href="https://github.com/Naddiseo/dart-sprintf.git" rel="nofollow">https://github.com/Naddiseo/dart-sprintf.git</a></li> <li>Switch to the debugger_ide_test branch</li> <li><p>On console (not in the editor) run <code>dart test/sprintf_test.dart</code> The output should be:</p> <p><code>decimal=1, exp=0, digits=[5, 4, 6, 6]</code></p></li> <li><p>Next, fire up the editor, and open the folder.</p></li> <li>Run the same file, and it should print out the same result.</li> <li>Now for the weird part. Set a break point in lib/src/formatters/float_formatter.dart:17 which is the first line of the constructor.</li> <li>Run the test file in the editor again then continue once it gets the break point. </li> </ul> <p>With the breakpoint I'm getting the following output:</p> <pre><code>decimal=1, exp=0, digits=[0, 0, 5, 4, 6, 6] </code></pre> <p>I've attributed it to the <code>List&lt;String&gt;</code> constructor, which seems to initialise to not be empty. </p> <p>Does anyone else get this problem? I've tried to condense this into a testable single file, but have failed to reproduce; I'm only able to reproduce it in the actual project.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload