Unique character lookup












3














I'm solving 387. First Unique Character in a String LeetCode problem defined as:




Given a string, find the first non-repeating character in it and return it's index. If it doesn't exist, return -1.



Examples:



s = "leetcode"
return 0.

s = "loveleetcode",
return 2.


Note: You may assume the string contain only lowercase letters.




Taking advantage of the input being fully lowercase ASCII I created two bit vectors to track when we encounter a character for the first and second time.



Can this code be improved further? LeetCode says that below code is better than 94.33% solutions. What else could have been done by the last 5.67% solutions that they were better?



class Solution {

public int firstUniqChar(String s) {
int firstSpot = 0;
int secondSpot = 0;
char chars = s.toCharArray();

for (char c : chars) {
int mask = 1 << c - 'a';
if ((firstSpot & mask) == 0) {
firstSpot |= mask;
} else if ((secondSpot & mask) == 0) {
secondSpot |= mask;
}
}

int i = 0;
for (char c : chars) {
int mask = 1 << c - 'a';
if ((secondSpot & mask) == 0) {
return i;
}
i++;
}
return -1;
}

}


LeetCode score



Are there tricks that can be done to improve the LeetCode score? It seems that enhanced for-each loop performs better than standard for loop but I can't prove it. It's an observation based on few of my previous submissions.










share|improve this question




















  • 1




    I would not recommend the bitfield unless you need it for memory usage--an int array will perform better than bits (Writing bitfields requires the compiler to read/update/write to memory instead of just write).
    – Bill K
    Nov 20 at 0:35










  • @BillK Except firstSpot & secondSpot are local variables; they may not incur any memory cycles.
    – AJNeufeld
    Nov 20 at 3:11
















3














I'm solving 387. First Unique Character in a String LeetCode problem defined as:




Given a string, find the first non-repeating character in it and return it's index. If it doesn't exist, return -1.



Examples:



s = "leetcode"
return 0.

s = "loveleetcode",
return 2.


Note: You may assume the string contain only lowercase letters.




Taking advantage of the input being fully lowercase ASCII I created two bit vectors to track when we encounter a character for the first and second time.



Can this code be improved further? LeetCode says that below code is better than 94.33% solutions. What else could have been done by the last 5.67% solutions that they were better?



class Solution {

public int firstUniqChar(String s) {
int firstSpot = 0;
int secondSpot = 0;
char chars = s.toCharArray();

for (char c : chars) {
int mask = 1 << c - 'a';
if ((firstSpot & mask) == 0) {
firstSpot |= mask;
} else if ((secondSpot & mask) == 0) {
secondSpot |= mask;
}
}

int i = 0;
for (char c : chars) {
int mask = 1 << c - 'a';
if ((secondSpot & mask) == 0) {
return i;
}
i++;
}
return -1;
}

}


LeetCode score



Are there tricks that can be done to improve the LeetCode score? It seems that enhanced for-each loop performs better than standard for loop but I can't prove it. It's an observation based on few of my previous submissions.










share|improve this question




















  • 1




    I would not recommend the bitfield unless you need it for memory usage--an int array will perform better than bits (Writing bitfields requires the compiler to read/update/write to memory instead of just write).
    – Bill K
    Nov 20 at 0:35










  • @BillK Except firstSpot & secondSpot are local variables; they may not incur any memory cycles.
    – AJNeufeld
    Nov 20 at 3:11














3












3








3


1





I'm solving 387. First Unique Character in a String LeetCode problem defined as:




Given a string, find the first non-repeating character in it and return it's index. If it doesn't exist, return -1.



Examples:



s = "leetcode"
return 0.

s = "loveleetcode",
return 2.


Note: You may assume the string contain only lowercase letters.




Taking advantage of the input being fully lowercase ASCII I created two bit vectors to track when we encounter a character for the first and second time.



Can this code be improved further? LeetCode says that below code is better than 94.33% solutions. What else could have been done by the last 5.67% solutions that they were better?



class Solution {

public int firstUniqChar(String s) {
int firstSpot = 0;
int secondSpot = 0;
char chars = s.toCharArray();

for (char c : chars) {
int mask = 1 << c - 'a';
if ((firstSpot & mask) == 0) {
firstSpot |= mask;
} else if ((secondSpot & mask) == 0) {
secondSpot |= mask;
}
}

int i = 0;
for (char c : chars) {
int mask = 1 << c - 'a';
if ((secondSpot & mask) == 0) {
return i;
}
i++;
}
return -1;
}

}


LeetCode score



Are there tricks that can be done to improve the LeetCode score? It seems that enhanced for-each loop performs better than standard for loop but I can't prove it. It's an observation based on few of my previous submissions.










share|improve this question















I'm solving 387. First Unique Character in a String LeetCode problem defined as:




Given a string, find the first non-repeating character in it and return it's index. If it doesn't exist, return -1.



Examples:



s = "leetcode"
return 0.

s = "loveleetcode",
return 2.


Note: You may assume the string contain only lowercase letters.




Taking advantage of the input being fully lowercase ASCII I created two bit vectors to track when we encounter a character for the first and second time.



Can this code be improved further? LeetCode says that below code is better than 94.33% solutions. What else could have been done by the last 5.67% solutions that they were better?



class Solution {

public int firstUniqChar(String s) {
int firstSpot = 0;
int secondSpot = 0;
char chars = s.toCharArray();

for (char c : chars) {
int mask = 1 << c - 'a';
if ((firstSpot & mask) == 0) {
firstSpot |= mask;
} else if ((secondSpot & mask) == 0) {
secondSpot |= mask;
}
}

int i = 0;
for (char c : chars) {
int mask = 1 << c - 'a';
if ((secondSpot & mask) == 0) {
return i;
}
i++;
}
return -1;
}

}


LeetCode score



Are there tricks that can be done to improve the LeetCode score? It seems that enhanced for-each loop performs better than standard for loop but I can't prove it. It's an observation based on few of my previous submissions.







java algorithm






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 at 1:23









Jamal

30.2k11116226




30.2k11116226










asked Nov 19 at 23:05









Karol Dowbecki

1184




1184








  • 1




    I would not recommend the bitfield unless you need it for memory usage--an int array will perform better than bits (Writing bitfields requires the compiler to read/update/write to memory instead of just write).
    – Bill K
    Nov 20 at 0:35










  • @BillK Except firstSpot & secondSpot are local variables; they may not incur any memory cycles.
    – AJNeufeld
    Nov 20 at 3:11














  • 1




    I would not recommend the bitfield unless you need it for memory usage--an int array will perform better than bits (Writing bitfields requires the compiler to read/update/write to memory instead of just write).
    – Bill K
    Nov 20 at 0:35










  • @BillK Except firstSpot & secondSpot are local variables; they may not incur any memory cycles.
    – AJNeufeld
    Nov 20 at 3:11








1




1




I would not recommend the bitfield unless you need it for memory usage--an int array will perform better than bits (Writing bitfields requires the compiler to read/update/write to memory instead of just write).
– Bill K
Nov 20 at 0:35




I would not recommend the bitfield unless you need it for memory usage--an int array will perform better than bits (Writing bitfields requires the compiler to read/update/write to memory instead of just write).
– Bill K
Nov 20 at 0:35












@BillK Except firstSpot & secondSpot are local variables; they may not incur any memory cycles.
– AJNeufeld
Nov 20 at 3:11




@BillK Except firstSpot & secondSpot are local variables; they may not incur any memory cycles.
– AJNeufeld
Nov 20 at 3:11










5 Answers
5






active

oldest

votes


















4















  • When in doubt, profile. We may theorize about possible optimizations, but only the profiler can definitely say where the program does spend time.



  • That said,





    • the first/second spot logic looks suboptimal. Consider



      if ((firstSpot & mask) != 0) {
      secondSpot |= mask;
      } else {
      firstSpot |= mask;
      }



    (using else may also be redundant).




    • It is unclear (to me) how for (char c : chars) over the char array fares against other techniques. This could be an entertaining reading.


    Yet again, profile.



  • Strictly speaking, the challenge only says the string contain only lowercase letters, but does not specify the locale.







share|improve this answer























  • @AJNeufeld OK. Got carried away.
    – vnp
    Nov 20 at 0:27










  • @AJNeufeld I should not RUI.
    – vnp
    Nov 20 at 0:31










  • RUI? Is that “Reply Under the Influence”?
    – AJNeufeld
    Nov 20 at 0:34










  • @AJNeufeld Almost. "Review Under the Influence".
    – vnp
    Nov 20 at 0:35






  • 1




    @SylvainLeroux I have no idea. Even without the accented characters, the code fails for languages with more than 32 lowercase letters (like Russian).I strongly suspect however that the blame should be on a problem statement, rather than the solution.
    – vnp
    Nov 20 at 20:53



















3














Some suggestions:




  • You could get rid of the class and put the entire method contents within your main method; that'll at least get rid of an instantiation.

  • I'm not sure whether 'a' is converted to an integer at compilation time or runtime. Try using 0x61 instead.

  • You can avoid converting to a char array.






share|improve this answer























  • LeetCode gives a method signature to fill, I don't believe I can change that.
    – Karol Dowbecki
    Nov 19 at 23:48





















3














You don’t need to check if the second spot has been filled in; just unconditionally set it.



if ((firstSpot & mask) == 0) {
firstSpot |= mask;
} else {
secondSpot |= mask;
}




Avoiding branching usually helps.



secondSpot |= mask & firstSpot; // sets second spot bit unless first spot bit is still zero
firstSpot |= mask;




After the first loop finishes, if firstSpot == secondSpot, you can immediately return -1






share|improve this answer































    1















    Taking advantage of the input being fully lowercase ASCII




    While it says that all characters are lowercase it doesn't say anything about ASCII. Given that it passed the tests that was okay, but generally lowercase doesn't imply ASCII.




    I created two bit vectors to track when we encounter a character for the first and second time.




    And that really requires the input to be ASCII. Because char can hold any value between 0 and 65535 the << might not be safe to use, I'm not a Java programmer but it could result in an exception, an unwanted result or undefined behavior.



    But if it's just ASCII characters between 'a' and 'a' + 31 the approach will work.




    Can this code be improved further? LeetCode says that below code is better than 94.33% solutions. What else could have been done by the last 5.67% solutions that they were better?




    It seems like your definition of "improvement" is "better performance". But that again is probably not how every programmer defines "improvement".



    As far as I see it:




    • You don't have any comments,

    • you don't have tests,

    • your variables have odd names. For example: firstSpot is a weird name for a bitarray that represents if a character has been found once, ...

    • you don't have benchmarks


    So my personal opinion is: There's lots of room for improvement.





    I also have some thoughts about the algorithm and how it could be improved. As said I'm not a Java programmer so I'm just sharing some thoughts:




    • You iterate over the string three times while it would be possible to iterate only once. You could create an array of integers (26 elements long) to store the first occurrence of each character and after the loop you look at the elements that only occurred once and then take the minimum of the indices. Since you iterate with index you can remove the toCharArray and index into the string directly (which incidentally may be a faster way to iterate over the string altogether, according to this StackOverflow Q+A).


    • In case there is no single character you might even stop the loop early. As soon as your secondSpot bitarray contains an entry for all ASCII characters you can immediately return -1.


    • As the others mentioned you could even drop some of the "branches" inside the loop which may give some performance improvement.







    share|improve this answer































      0














      I'd use a dictionary. Loop once over the characters in the string. For each found character, create an entry in the dictionary, the character being the key, the value being the index. If a character exists in the dictionary, set the value to [length of word] + 1.
      When all characters are seen, loop over the dictionary. Pick the least (first by my testing) index encountered less than [length of word] + 1 and return it. If no value is returned, return -1.



      Here is my shot (admittedly in c#).



      int firstUniqCharInString(string s)
      {
      Dictionary<char, int> seen = new Dictionary<char, int>();
      int t = -1;
      foreach (char c in s)
      {
      t++;
      if (seen.ContainsKey(c))
      {
      seen[c] = s.Length + 1;
      }
      else
      {
      seen.Add(c, t);
      }

      }
      int len = s.Length + 1;
      foreach(KeyValuePair<char, int> pair in seen)
      {
      if(pair.Value < len) {
      return pair.Value;
      }
      }
      return (-1);
      }





      share|improve this answer





















      • A generic dictionary implementation (which, in this case, is a hash table) will never beat direct lookup in a contiguous array or bit vector. Consequently, this will be much slower than OP’s solution. Apart from that you don’t need to add 1 to the string length. s.Length alone is sufficient. Thirdly, you are performing two lookups per character, which is also inefficient. Unfortunately C#’s S.C.G.Dictionary does not contain any way of reducing this to a single lookup but other languages/APIs do. Lastly, it’s unclear why you start off t at -1 and pre-increment it. Start at 0 instead.
        – Konrad Rudolph
        Nov 20 at 14:31












      • You have presented an alternative solution, but haven't reviewed the code. Please explain your reasoning (how your solution works and why it is better than the original) so that the author and other readers can learn from your thought process.
        – Mast
        Nov 20 at 14:31










      • I was trying to avoid checking each character twice, the main point of my answer. Looking at the accepted answer here: stackoverflow.com/questions/53383866/… checking twice might be the way to go anyway. Even after slightly optimizing my code after Konrads point, I think my code will be less efficient than the OP's. Would explaining my idea help anyway? I would downvote my answer or just remove it altogether.
        – user185166
        Nov 20 at 15:14











      Your Answer





      StackExchange.ifUsing("editor", function () {
      return StackExchange.using("mathjaxEditing", function () {
      StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
      StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
      });
      });
      }, "mathjax-editing");

      StackExchange.ifUsing("editor", function () {
      StackExchange.using("externalEditor", function () {
      StackExchange.using("snippets", function () {
      StackExchange.snippets.init();
      });
      });
      }, "code-snippets");

      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "196"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f208020%2funique-character-lookup%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      5 Answers
      5






      active

      oldest

      votes








      5 Answers
      5






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      4















      • When in doubt, profile. We may theorize about possible optimizations, but only the profiler can definitely say where the program does spend time.



      • That said,





        • the first/second spot logic looks suboptimal. Consider



          if ((firstSpot & mask) != 0) {
          secondSpot |= mask;
          } else {
          firstSpot |= mask;
          }



        (using else may also be redundant).




        • It is unclear (to me) how for (char c : chars) over the char array fares against other techniques. This could be an entertaining reading.


        Yet again, profile.



      • Strictly speaking, the challenge only says the string contain only lowercase letters, but does not specify the locale.







      share|improve this answer























      • @AJNeufeld OK. Got carried away.
        – vnp
        Nov 20 at 0:27










      • @AJNeufeld I should not RUI.
        – vnp
        Nov 20 at 0:31










      • RUI? Is that “Reply Under the Influence”?
        – AJNeufeld
        Nov 20 at 0:34










      • @AJNeufeld Almost. "Review Under the Influence".
        – vnp
        Nov 20 at 0:35






      • 1




        @SylvainLeroux I have no idea. Even without the accented characters, the code fails for languages with more than 32 lowercase letters (like Russian).I strongly suspect however that the blame should be on a problem statement, rather than the solution.
        – vnp
        Nov 20 at 20:53
















      4















      • When in doubt, profile. We may theorize about possible optimizations, but only the profiler can definitely say where the program does spend time.



      • That said,





        • the first/second spot logic looks suboptimal. Consider



          if ((firstSpot & mask) != 0) {
          secondSpot |= mask;
          } else {
          firstSpot |= mask;
          }



        (using else may also be redundant).




        • It is unclear (to me) how for (char c : chars) over the char array fares against other techniques. This could be an entertaining reading.


        Yet again, profile.



      • Strictly speaking, the challenge only says the string contain only lowercase letters, but does not specify the locale.







      share|improve this answer























      • @AJNeufeld OK. Got carried away.
        – vnp
        Nov 20 at 0:27










      • @AJNeufeld I should not RUI.
        – vnp
        Nov 20 at 0:31










      • RUI? Is that “Reply Under the Influence”?
        – AJNeufeld
        Nov 20 at 0:34










      • @AJNeufeld Almost. "Review Under the Influence".
        – vnp
        Nov 20 at 0:35






      • 1




        @SylvainLeroux I have no idea. Even without the accented characters, the code fails for languages with more than 32 lowercase letters (like Russian).I strongly suspect however that the blame should be on a problem statement, rather than the solution.
        – vnp
        Nov 20 at 20:53














      4












      4








      4







      • When in doubt, profile. We may theorize about possible optimizations, but only the profiler can definitely say where the program does spend time.



      • That said,





        • the first/second spot logic looks suboptimal. Consider



          if ((firstSpot & mask) != 0) {
          secondSpot |= mask;
          } else {
          firstSpot |= mask;
          }



        (using else may also be redundant).




        • It is unclear (to me) how for (char c : chars) over the char array fares against other techniques. This could be an entertaining reading.


        Yet again, profile.



      • Strictly speaking, the challenge only says the string contain only lowercase letters, but does not specify the locale.







      share|improve this answer















      • When in doubt, profile. We may theorize about possible optimizations, but only the profiler can definitely say where the program does spend time.



      • That said,





        • the first/second spot logic looks suboptimal. Consider



          if ((firstSpot & mask) != 0) {
          secondSpot |= mask;
          } else {
          firstSpot |= mask;
          }



        (using else may also be redundant).




        • It is unclear (to me) how for (char c : chars) over the char array fares against other techniques. This could be an entertaining reading.


        Yet again, profile.



      • Strictly speaking, the challenge only says the string contain only lowercase letters, but does not specify the locale.








      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Nov 20 at 0:30

























      answered Nov 20 at 0:00









      vnp

      38.5k13097




      38.5k13097












      • @AJNeufeld OK. Got carried away.
        – vnp
        Nov 20 at 0:27










      • @AJNeufeld I should not RUI.
        – vnp
        Nov 20 at 0:31










      • RUI? Is that “Reply Under the Influence”?
        – AJNeufeld
        Nov 20 at 0:34










      • @AJNeufeld Almost. "Review Under the Influence".
        – vnp
        Nov 20 at 0:35






      • 1




        @SylvainLeroux I have no idea. Even without the accented characters, the code fails for languages with more than 32 lowercase letters (like Russian).I strongly suspect however that the blame should be on a problem statement, rather than the solution.
        – vnp
        Nov 20 at 20:53


















      • @AJNeufeld OK. Got carried away.
        – vnp
        Nov 20 at 0:27










      • @AJNeufeld I should not RUI.
        – vnp
        Nov 20 at 0:31










      • RUI? Is that “Reply Under the Influence”?
        – AJNeufeld
        Nov 20 at 0:34










      • @AJNeufeld Almost. "Review Under the Influence".
        – vnp
        Nov 20 at 0:35






      • 1




        @SylvainLeroux I have no idea. Even without the accented characters, the code fails for languages with more than 32 lowercase letters (like Russian).I strongly suspect however that the blame should be on a problem statement, rather than the solution.
        – vnp
        Nov 20 at 20:53
















      @AJNeufeld OK. Got carried away.
      – vnp
      Nov 20 at 0:27




      @AJNeufeld OK. Got carried away.
      – vnp
      Nov 20 at 0:27












      @AJNeufeld I should not RUI.
      – vnp
      Nov 20 at 0:31




      @AJNeufeld I should not RUI.
      – vnp
      Nov 20 at 0:31












      RUI? Is that “Reply Under the Influence”?
      – AJNeufeld
      Nov 20 at 0:34




      RUI? Is that “Reply Under the Influence”?
      – AJNeufeld
      Nov 20 at 0:34












      @AJNeufeld Almost. "Review Under the Influence".
      – vnp
      Nov 20 at 0:35




      @AJNeufeld Almost. "Review Under the Influence".
      – vnp
      Nov 20 at 0:35




      1




      1




      @SylvainLeroux I have no idea. Even without the accented characters, the code fails for languages with more than 32 lowercase letters (like Russian).I strongly suspect however that the blame should be on a problem statement, rather than the solution.
      – vnp
      Nov 20 at 20:53




      @SylvainLeroux I have no idea. Even without the accented characters, the code fails for languages with more than 32 lowercase letters (like Russian).I strongly suspect however that the blame should be on a problem statement, rather than the solution.
      – vnp
      Nov 20 at 20:53













      3














      Some suggestions:




      • You could get rid of the class and put the entire method contents within your main method; that'll at least get rid of an instantiation.

      • I'm not sure whether 'a' is converted to an integer at compilation time or runtime. Try using 0x61 instead.

      • You can avoid converting to a char array.






      share|improve this answer























      • LeetCode gives a method signature to fill, I don't believe I can change that.
        – Karol Dowbecki
        Nov 19 at 23:48


















      3














      Some suggestions:




      • You could get rid of the class and put the entire method contents within your main method; that'll at least get rid of an instantiation.

      • I'm not sure whether 'a' is converted to an integer at compilation time or runtime. Try using 0x61 instead.

      • You can avoid converting to a char array.






      share|improve this answer























      • LeetCode gives a method signature to fill, I don't believe I can change that.
        – Karol Dowbecki
        Nov 19 at 23:48
















      3












      3








      3






      Some suggestions:




      • You could get rid of the class and put the entire method contents within your main method; that'll at least get rid of an instantiation.

      • I'm not sure whether 'a' is converted to an integer at compilation time or runtime. Try using 0x61 instead.

      • You can avoid converting to a char array.






      share|improve this answer














      Some suggestions:




      • You could get rid of the class and put the entire method contents within your main method; that'll at least get rid of an instantiation.

      • I'm not sure whether 'a' is converted to an integer at compilation time or runtime. Try using 0x61 instead.

      • You can avoid converting to a char array.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Nov 19 at 23:49

























      answered Nov 19 at 23:47









      l0b0

      4,182923




      4,182923












      • LeetCode gives a method signature to fill, I don't believe I can change that.
        – Karol Dowbecki
        Nov 19 at 23:48




















      • LeetCode gives a method signature to fill, I don't believe I can change that.
        – Karol Dowbecki
        Nov 19 at 23:48


















      LeetCode gives a method signature to fill, I don't believe I can change that.
      – Karol Dowbecki
      Nov 19 at 23:48






      LeetCode gives a method signature to fill, I don't believe I can change that.
      – Karol Dowbecki
      Nov 19 at 23:48













      3














      You don’t need to check if the second spot has been filled in; just unconditionally set it.



      if ((firstSpot & mask) == 0) {
      firstSpot |= mask;
      } else {
      secondSpot |= mask;
      }




      Avoiding branching usually helps.



      secondSpot |= mask & firstSpot; // sets second spot bit unless first spot bit is still zero
      firstSpot |= mask;




      After the first loop finishes, if firstSpot == secondSpot, you can immediately return -1






      share|improve this answer




























        3














        You don’t need to check if the second spot has been filled in; just unconditionally set it.



        if ((firstSpot & mask) == 0) {
        firstSpot |= mask;
        } else {
        secondSpot |= mask;
        }




        Avoiding branching usually helps.



        secondSpot |= mask & firstSpot; // sets second spot bit unless first spot bit is still zero
        firstSpot |= mask;




        After the first loop finishes, if firstSpot == secondSpot, you can immediately return -1






        share|improve this answer


























          3












          3








          3






          You don’t need to check if the second spot has been filled in; just unconditionally set it.



          if ((firstSpot & mask) == 0) {
          firstSpot |= mask;
          } else {
          secondSpot |= mask;
          }




          Avoiding branching usually helps.



          secondSpot |= mask & firstSpot; // sets second spot bit unless first spot bit is still zero
          firstSpot |= mask;




          After the first loop finishes, if firstSpot == secondSpot, you can immediately return -1






          share|improve this answer














          You don’t need to check if the second spot has been filled in; just unconditionally set it.



          if ((firstSpot & mask) == 0) {
          firstSpot |= mask;
          } else {
          secondSpot |= mask;
          }




          Avoiding branching usually helps.



          secondSpot |= mask & firstSpot; // sets second spot bit unless first spot bit is still zero
          firstSpot |= mask;




          After the first loop finishes, if firstSpot == secondSpot, you can immediately return -1







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 21 at 5:36

























          answered Nov 19 at 23:59









          AJNeufeld

          4,147318




          4,147318























              1















              Taking advantage of the input being fully lowercase ASCII




              While it says that all characters are lowercase it doesn't say anything about ASCII. Given that it passed the tests that was okay, but generally lowercase doesn't imply ASCII.




              I created two bit vectors to track when we encounter a character for the first and second time.




              And that really requires the input to be ASCII. Because char can hold any value between 0 and 65535 the << might not be safe to use, I'm not a Java programmer but it could result in an exception, an unwanted result or undefined behavior.



              But if it's just ASCII characters between 'a' and 'a' + 31 the approach will work.




              Can this code be improved further? LeetCode says that below code is better than 94.33% solutions. What else could have been done by the last 5.67% solutions that they were better?




              It seems like your definition of "improvement" is "better performance". But that again is probably not how every programmer defines "improvement".



              As far as I see it:




              • You don't have any comments,

              • you don't have tests,

              • your variables have odd names. For example: firstSpot is a weird name for a bitarray that represents if a character has been found once, ...

              • you don't have benchmarks


              So my personal opinion is: There's lots of room for improvement.





              I also have some thoughts about the algorithm and how it could be improved. As said I'm not a Java programmer so I'm just sharing some thoughts:




              • You iterate over the string three times while it would be possible to iterate only once. You could create an array of integers (26 elements long) to store the first occurrence of each character and after the loop you look at the elements that only occurred once and then take the minimum of the indices. Since you iterate with index you can remove the toCharArray and index into the string directly (which incidentally may be a faster way to iterate over the string altogether, according to this StackOverflow Q+A).


              • In case there is no single character you might even stop the loop early. As soon as your secondSpot bitarray contains an entry for all ASCII characters you can immediately return -1.


              • As the others mentioned you could even drop some of the "branches" inside the loop which may give some performance improvement.







              share|improve this answer




























                1















                Taking advantage of the input being fully lowercase ASCII




                While it says that all characters are lowercase it doesn't say anything about ASCII. Given that it passed the tests that was okay, but generally lowercase doesn't imply ASCII.




                I created two bit vectors to track when we encounter a character for the first and second time.




                And that really requires the input to be ASCII. Because char can hold any value between 0 and 65535 the << might not be safe to use, I'm not a Java programmer but it could result in an exception, an unwanted result or undefined behavior.



                But if it's just ASCII characters between 'a' and 'a' + 31 the approach will work.




                Can this code be improved further? LeetCode says that below code is better than 94.33% solutions. What else could have been done by the last 5.67% solutions that they were better?




                It seems like your definition of "improvement" is "better performance". But that again is probably not how every programmer defines "improvement".



                As far as I see it:




                • You don't have any comments,

                • you don't have tests,

                • your variables have odd names. For example: firstSpot is a weird name for a bitarray that represents if a character has been found once, ...

                • you don't have benchmarks


                So my personal opinion is: There's lots of room for improvement.





                I also have some thoughts about the algorithm and how it could be improved. As said I'm not a Java programmer so I'm just sharing some thoughts:




                • You iterate over the string three times while it would be possible to iterate only once. You could create an array of integers (26 elements long) to store the first occurrence of each character and after the loop you look at the elements that only occurred once and then take the minimum of the indices. Since you iterate with index you can remove the toCharArray and index into the string directly (which incidentally may be a faster way to iterate over the string altogether, according to this StackOverflow Q+A).


                • In case there is no single character you might even stop the loop early. As soon as your secondSpot bitarray contains an entry for all ASCII characters you can immediately return -1.


                • As the others mentioned you could even drop some of the "branches" inside the loop which may give some performance improvement.







                share|improve this answer


























                  1












                  1








                  1







                  Taking advantage of the input being fully lowercase ASCII




                  While it says that all characters are lowercase it doesn't say anything about ASCII. Given that it passed the tests that was okay, but generally lowercase doesn't imply ASCII.




                  I created two bit vectors to track when we encounter a character for the first and second time.




                  And that really requires the input to be ASCII. Because char can hold any value between 0 and 65535 the << might not be safe to use, I'm not a Java programmer but it could result in an exception, an unwanted result or undefined behavior.



                  But if it's just ASCII characters between 'a' and 'a' + 31 the approach will work.




                  Can this code be improved further? LeetCode says that below code is better than 94.33% solutions. What else could have been done by the last 5.67% solutions that they were better?




                  It seems like your definition of "improvement" is "better performance". But that again is probably not how every programmer defines "improvement".



                  As far as I see it:




                  • You don't have any comments,

                  • you don't have tests,

                  • your variables have odd names. For example: firstSpot is a weird name for a bitarray that represents if a character has been found once, ...

                  • you don't have benchmarks


                  So my personal opinion is: There's lots of room for improvement.





                  I also have some thoughts about the algorithm and how it could be improved. As said I'm not a Java programmer so I'm just sharing some thoughts:




                  • You iterate over the string three times while it would be possible to iterate only once. You could create an array of integers (26 elements long) to store the first occurrence of each character and after the loop you look at the elements that only occurred once and then take the minimum of the indices. Since you iterate with index you can remove the toCharArray and index into the string directly (which incidentally may be a faster way to iterate over the string altogether, according to this StackOverflow Q+A).


                  • In case there is no single character you might even stop the loop early. As soon as your secondSpot bitarray contains an entry for all ASCII characters you can immediately return -1.


                  • As the others mentioned you could even drop some of the "branches" inside the loop which may give some performance improvement.







                  share|improve this answer















                  Taking advantage of the input being fully lowercase ASCII




                  While it says that all characters are lowercase it doesn't say anything about ASCII. Given that it passed the tests that was okay, but generally lowercase doesn't imply ASCII.




                  I created two bit vectors to track when we encounter a character for the first and second time.




                  And that really requires the input to be ASCII. Because char can hold any value between 0 and 65535 the << might not be safe to use, I'm not a Java programmer but it could result in an exception, an unwanted result or undefined behavior.



                  But if it's just ASCII characters between 'a' and 'a' + 31 the approach will work.




                  Can this code be improved further? LeetCode says that below code is better than 94.33% solutions. What else could have been done by the last 5.67% solutions that they were better?




                  It seems like your definition of "improvement" is "better performance". But that again is probably not how every programmer defines "improvement".



                  As far as I see it:




                  • You don't have any comments,

                  • you don't have tests,

                  • your variables have odd names. For example: firstSpot is a weird name for a bitarray that represents if a character has been found once, ...

                  • you don't have benchmarks


                  So my personal opinion is: There's lots of room for improvement.





                  I also have some thoughts about the algorithm and how it could be improved. As said I'm not a Java programmer so I'm just sharing some thoughts:




                  • You iterate over the string three times while it would be possible to iterate only once. You could create an array of integers (26 elements long) to store the first occurrence of each character and after the loop you look at the elements that only occurred once and then take the minimum of the indices. Since you iterate with index you can remove the toCharArray and index into the string directly (which incidentally may be a faster way to iterate over the string altogether, according to this StackOverflow Q+A).


                  • In case there is no single character you might even stop the loop early. As soon as your secondSpot bitarray contains an entry for all ASCII characters you can immediately return -1.


                  • As the others mentioned you could even drop some of the "branches" inside the loop which may give some performance improvement.








                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Nov 20 at 16:38

























                  answered Nov 20 at 15:34









                  MSeifert

                  580416




                  580416























                      0














                      I'd use a dictionary. Loop once over the characters in the string. For each found character, create an entry in the dictionary, the character being the key, the value being the index. If a character exists in the dictionary, set the value to [length of word] + 1.
                      When all characters are seen, loop over the dictionary. Pick the least (first by my testing) index encountered less than [length of word] + 1 and return it. If no value is returned, return -1.



                      Here is my shot (admittedly in c#).



                      int firstUniqCharInString(string s)
                      {
                      Dictionary<char, int> seen = new Dictionary<char, int>();
                      int t = -1;
                      foreach (char c in s)
                      {
                      t++;
                      if (seen.ContainsKey(c))
                      {
                      seen[c] = s.Length + 1;
                      }
                      else
                      {
                      seen.Add(c, t);
                      }

                      }
                      int len = s.Length + 1;
                      foreach(KeyValuePair<char, int> pair in seen)
                      {
                      if(pair.Value < len) {
                      return pair.Value;
                      }
                      }
                      return (-1);
                      }





                      share|improve this answer





















                      • A generic dictionary implementation (which, in this case, is a hash table) will never beat direct lookup in a contiguous array or bit vector. Consequently, this will be much slower than OP’s solution. Apart from that you don’t need to add 1 to the string length. s.Length alone is sufficient. Thirdly, you are performing two lookups per character, which is also inefficient. Unfortunately C#’s S.C.G.Dictionary does not contain any way of reducing this to a single lookup but other languages/APIs do. Lastly, it’s unclear why you start off t at -1 and pre-increment it. Start at 0 instead.
                        – Konrad Rudolph
                        Nov 20 at 14:31












                      • You have presented an alternative solution, but haven't reviewed the code. Please explain your reasoning (how your solution works and why it is better than the original) so that the author and other readers can learn from your thought process.
                        – Mast
                        Nov 20 at 14:31










                      • I was trying to avoid checking each character twice, the main point of my answer. Looking at the accepted answer here: stackoverflow.com/questions/53383866/… checking twice might be the way to go anyway. Even after slightly optimizing my code after Konrads point, I think my code will be less efficient than the OP's. Would explaining my idea help anyway? I would downvote my answer or just remove it altogether.
                        – user185166
                        Nov 20 at 15:14
















                      0














                      I'd use a dictionary. Loop once over the characters in the string. For each found character, create an entry in the dictionary, the character being the key, the value being the index. If a character exists in the dictionary, set the value to [length of word] + 1.
                      When all characters are seen, loop over the dictionary. Pick the least (first by my testing) index encountered less than [length of word] + 1 and return it. If no value is returned, return -1.



                      Here is my shot (admittedly in c#).



                      int firstUniqCharInString(string s)
                      {
                      Dictionary<char, int> seen = new Dictionary<char, int>();
                      int t = -1;
                      foreach (char c in s)
                      {
                      t++;
                      if (seen.ContainsKey(c))
                      {
                      seen[c] = s.Length + 1;
                      }
                      else
                      {
                      seen.Add(c, t);
                      }

                      }
                      int len = s.Length + 1;
                      foreach(KeyValuePair<char, int> pair in seen)
                      {
                      if(pair.Value < len) {
                      return pair.Value;
                      }
                      }
                      return (-1);
                      }





                      share|improve this answer





















                      • A generic dictionary implementation (which, in this case, is a hash table) will never beat direct lookup in a contiguous array or bit vector. Consequently, this will be much slower than OP’s solution. Apart from that you don’t need to add 1 to the string length. s.Length alone is sufficient. Thirdly, you are performing two lookups per character, which is also inefficient. Unfortunately C#’s S.C.G.Dictionary does not contain any way of reducing this to a single lookup but other languages/APIs do. Lastly, it’s unclear why you start off t at -1 and pre-increment it. Start at 0 instead.
                        – Konrad Rudolph
                        Nov 20 at 14:31












                      • You have presented an alternative solution, but haven't reviewed the code. Please explain your reasoning (how your solution works and why it is better than the original) so that the author and other readers can learn from your thought process.
                        – Mast
                        Nov 20 at 14:31










                      • I was trying to avoid checking each character twice, the main point of my answer. Looking at the accepted answer here: stackoverflow.com/questions/53383866/… checking twice might be the way to go anyway. Even after slightly optimizing my code after Konrads point, I think my code will be less efficient than the OP's. Would explaining my idea help anyway? I would downvote my answer or just remove it altogether.
                        – user185166
                        Nov 20 at 15:14














                      0












                      0








                      0






                      I'd use a dictionary. Loop once over the characters in the string. For each found character, create an entry in the dictionary, the character being the key, the value being the index. If a character exists in the dictionary, set the value to [length of word] + 1.
                      When all characters are seen, loop over the dictionary. Pick the least (first by my testing) index encountered less than [length of word] + 1 and return it. If no value is returned, return -1.



                      Here is my shot (admittedly in c#).



                      int firstUniqCharInString(string s)
                      {
                      Dictionary<char, int> seen = new Dictionary<char, int>();
                      int t = -1;
                      foreach (char c in s)
                      {
                      t++;
                      if (seen.ContainsKey(c))
                      {
                      seen[c] = s.Length + 1;
                      }
                      else
                      {
                      seen.Add(c, t);
                      }

                      }
                      int len = s.Length + 1;
                      foreach(KeyValuePair<char, int> pair in seen)
                      {
                      if(pair.Value < len) {
                      return pair.Value;
                      }
                      }
                      return (-1);
                      }





                      share|improve this answer












                      I'd use a dictionary. Loop once over the characters in the string. For each found character, create an entry in the dictionary, the character being the key, the value being the index. If a character exists in the dictionary, set the value to [length of word] + 1.
                      When all characters are seen, loop over the dictionary. Pick the least (first by my testing) index encountered less than [length of word] + 1 and return it. If no value is returned, return -1.



                      Here is my shot (admittedly in c#).



                      int firstUniqCharInString(string s)
                      {
                      Dictionary<char, int> seen = new Dictionary<char, int>();
                      int t = -1;
                      foreach (char c in s)
                      {
                      t++;
                      if (seen.ContainsKey(c))
                      {
                      seen[c] = s.Length + 1;
                      }
                      else
                      {
                      seen.Add(c, t);
                      }

                      }
                      int len = s.Length + 1;
                      foreach(KeyValuePair<char, int> pair in seen)
                      {
                      if(pair.Value < len) {
                      return pair.Value;
                      }
                      }
                      return (-1);
                      }






                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Nov 20 at 12:14









                      user185166

                      1




                      1












                      • A generic dictionary implementation (which, in this case, is a hash table) will never beat direct lookup in a contiguous array or bit vector. Consequently, this will be much slower than OP’s solution. Apart from that you don’t need to add 1 to the string length. s.Length alone is sufficient. Thirdly, you are performing two lookups per character, which is also inefficient. Unfortunately C#’s S.C.G.Dictionary does not contain any way of reducing this to a single lookup but other languages/APIs do. Lastly, it’s unclear why you start off t at -1 and pre-increment it. Start at 0 instead.
                        – Konrad Rudolph
                        Nov 20 at 14:31












                      • You have presented an alternative solution, but haven't reviewed the code. Please explain your reasoning (how your solution works and why it is better than the original) so that the author and other readers can learn from your thought process.
                        – Mast
                        Nov 20 at 14:31










                      • I was trying to avoid checking each character twice, the main point of my answer. Looking at the accepted answer here: stackoverflow.com/questions/53383866/… checking twice might be the way to go anyway. Even after slightly optimizing my code after Konrads point, I think my code will be less efficient than the OP's. Would explaining my idea help anyway? I would downvote my answer or just remove it altogether.
                        – user185166
                        Nov 20 at 15:14


















                      • A generic dictionary implementation (which, in this case, is a hash table) will never beat direct lookup in a contiguous array or bit vector. Consequently, this will be much slower than OP’s solution. Apart from that you don’t need to add 1 to the string length. s.Length alone is sufficient. Thirdly, you are performing two lookups per character, which is also inefficient. Unfortunately C#’s S.C.G.Dictionary does not contain any way of reducing this to a single lookup but other languages/APIs do. Lastly, it’s unclear why you start off t at -1 and pre-increment it. Start at 0 instead.
                        – Konrad Rudolph
                        Nov 20 at 14:31












                      • You have presented an alternative solution, but haven't reviewed the code. Please explain your reasoning (how your solution works and why it is better than the original) so that the author and other readers can learn from your thought process.
                        – Mast
                        Nov 20 at 14:31










                      • I was trying to avoid checking each character twice, the main point of my answer. Looking at the accepted answer here: stackoverflow.com/questions/53383866/… checking twice might be the way to go anyway. Even after slightly optimizing my code after Konrads point, I think my code will be less efficient than the OP's. Would explaining my idea help anyway? I would downvote my answer or just remove it altogether.
                        – user185166
                        Nov 20 at 15:14
















                      A generic dictionary implementation (which, in this case, is a hash table) will never beat direct lookup in a contiguous array or bit vector. Consequently, this will be much slower than OP’s solution. Apart from that you don’t need to add 1 to the string length. s.Length alone is sufficient. Thirdly, you are performing two lookups per character, which is also inefficient. Unfortunately C#’s S.C.G.Dictionary does not contain any way of reducing this to a single lookup but other languages/APIs do. Lastly, it’s unclear why you start off t at -1 and pre-increment it. Start at 0 instead.
                      – Konrad Rudolph
                      Nov 20 at 14:31






                      A generic dictionary implementation (which, in this case, is a hash table) will never beat direct lookup in a contiguous array or bit vector. Consequently, this will be much slower than OP’s solution. Apart from that you don’t need to add 1 to the string length. s.Length alone is sufficient. Thirdly, you are performing two lookups per character, which is also inefficient. Unfortunately C#’s S.C.G.Dictionary does not contain any way of reducing this to a single lookup but other languages/APIs do. Lastly, it’s unclear why you start off t at -1 and pre-increment it. Start at 0 instead.
                      – Konrad Rudolph
                      Nov 20 at 14:31














                      You have presented an alternative solution, but haven't reviewed the code. Please explain your reasoning (how your solution works and why it is better than the original) so that the author and other readers can learn from your thought process.
                      – Mast
                      Nov 20 at 14:31




                      You have presented an alternative solution, but haven't reviewed the code. Please explain your reasoning (how your solution works and why it is better than the original) so that the author and other readers can learn from your thought process.
                      – Mast
                      Nov 20 at 14:31












                      I was trying to avoid checking each character twice, the main point of my answer. Looking at the accepted answer here: stackoverflow.com/questions/53383866/… checking twice might be the way to go anyway. Even after slightly optimizing my code after Konrads point, I think my code will be less efficient than the OP's. Would explaining my idea help anyway? I would downvote my answer or just remove it altogether.
                      – user185166
                      Nov 20 at 15:14




                      I was trying to avoid checking each character twice, the main point of my answer. Looking at the accepted answer here: stackoverflow.com/questions/53383866/… checking twice might be the way to go anyway. Even after slightly optimizing my code after Konrads point, I think my code will be less efficient than the OP's. Would explaining my idea help anyway? I would downvote my answer or just remove it altogether.
                      – user185166
                      Nov 20 at 15:14


















                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Code Review Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      Use MathJax to format equations. MathJax reference.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f208020%2funique-character-lookup%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                      Alcedinidae

                      RAC Tourist Trophy