335

How to convert String to CharSequence in Java?

Improve this question
5
  • 27
    The question is kind of non sensical. Converting a String to a CharSequence is like converting a flute to a musical instrument. A String already is a CharSequence. The String class implements the CharSequence interface. Commented May 22, 2014 at 21:29
  • 4
    The OP's confusion might stem from not knowing what it means to program to an interface Commented Nov 14, 2014 at 14:10
  • 14
    @JeffScottBrown the question actually makes sense, it's a legitimate wonder to anyone reading through the Android or Java doc and missing the detail that CharSequence is not a class. Your comment helped me, but if the question had not been worded the way it is, i wouldn't have found it and have spent more time looking for an answer than it's really worth ;) Commented Mar 12, 2015 at 14:42
  • I came to this question in the context of a groovy Problem: Exception groovy.lang.MissingMethodException: No signature of method: static java.util.regex.Pattern.matcher() is applicable for argument types: (java.lang.String) Commented May 12, 2015 at 13:41
  • 1
    Here's how I'd advice @JeffScottBrown to reword his comment- "The String class implements (IS-A) the CharSequence interface so you can pass in a String in place of a CharSequence. It's like how you could refer to a flute as a musical instrument because a flute IS-A musical instrument" Commented Jul 13, 2017 at 0:42

6 Answers 6

Reset to default
310

Since String IS-A CharSequence, you can pass a String wherever you need a CharSequence, or assign a String to a CharSequence:

CharSequence cs = "string";
String s = cs.toString();
foo(s); // prints "string"

public void foo(CharSequence cs) { 
  System.out.println(cs);
}

If you want to convert a CharSequence to a String, just use the toString method that must be implemented by every concrete implementation of CharSequence.

Improve this answer
Sign up to request clarification or add additional context in comments.

7 Comments

Except that you can't assign a CharSequence to a String without an explicit cast.
Fixed the example, thanks. I meant the other way around, i.e., assign a String to a CharSequence.
You are correct. It is indeed an interface. However, that code does not instantiate a CharSequence. It simply assigns an instance of String to a CharSequence variable, and since String implements the CharSequence interface, the code works.
This is not the answer. Question is String -> to -> CharSequence. Answer is reverse.
This answers both. Poster first trivially resolves the String -> CharSequence problem by explaining that a String IS a CharSequence. Then poster answers how to go from CharSequence to String.
|
81

Straight answer:

String s = "Hello World!";

// String => CharSequence conversion:

CharSequence cs = s;  // String is already a CharSequence

CharSequence is an interface, and the String class implements CharSequence.

Improve this answer

Comments

14

CharSequence is an interface and String is its one of the implementations other than StringBuilder, StringBuffer and many other.

So, just as you use InterfaceName i = new ItsImplementation(), you can use CharSequence cs = new String("string") or simply CharSequence cs = "string";

Improve this answer

Comments

4

You can use 

CharSequence[] cs = String[] {"String to CharSequence"};
Improve this answer

3 Comments

Welcome to Stack Overflow Lucas. Please provide more explanation than a code snippet. It may be obvious for us, but help others letting them know why this code answer the question.
Wrapping a string into an array doesn't help making a point that String is a CharSequence (and hence that array of CharSequence is array of String).
CharSequence[] cs = new CharSequence[] {"String to CharSequence"};
3

That's a good question! You may get into troubles if you invoke API that uses generics and want to assign or return that result with a different subtype of the generic type. Java 8 helps to transform:

    List<String> input = new LinkedList<>(Arrays.asList("a", "b", "c"));
    List<CharSequence> result;
    
//    result = input; // <-- Type mismatch: cannot convert from List<String> to List<CharSequence>
    result = input.stream().collect(Collectors.toList());
    
    System.out.println(result);
Improve this answer

Comments

2

Attempting to provide some (possible) context for OP's question by posting my own trouble. I'm working in Scala, but the error messages I'm getting all reference Java types, and the error message reads a lot like the compiler complaining that CharSequence is not a String. I confirmed in the source code that String implements the CharSequence interface, but the error message draws attention to the difference between String and CharSequence while hiding the real source of the trouble:

scala> cols
res8: Iterable[String] = List(Item, a, b)

scala> val header = String.join(",", cols)
<console>:13: error: overloaded method value join with alternatives:
  (x$1: CharSequence,x$2: java.lang.Iterable[_ <: CharSequence])String <and>
  (x$1: CharSequence,x$2: CharSequence*)String
 cannot be applied to (String, Iterable[String])
       val header = String.join(",", cols)

I was able to fix this problem with the realization that the problem wasn't String / CharSequence, but rather a mismatch between java.lang.Iterable and Scala's built-in Iterable.

scala> val header = String.join(",", coll: _*)
header: String = Item,a,b

My particular problem can also be solved via the answers at Scala: join an iterable of strings

In summary, OP and others who come across similar problems should parse the error messages very closely and see what other type conversions might be involved.

Improve this answer

1 Comment

I had another similar error (in scala) trying to use the String.replace method with argument types (Char), but it needs two arguments, so I added the empty String as the second argument (which I assumed was the default) and converted the first argument to String (since it needed to match either both Char or CharSequence. So, mine was another example of closely reading the argument type options vs. my own method call.