How should I implement Default Associated Values with Swift Enums? -

-

swift question there way of having enum type 1 case can have associated value.

i have api gives me available filters, it's unlikely possible api add additional filter types. if api sends unknown filter type want keep information associated enum.

below different ideas had doing this.

my first 2 tries didn't compile. third try feels bit clunky.

does have better way of doing this? think shouldn't use enum problem?

typealias apifilteridentifier = string  /* not compile */ enum enumtestassociatedvaleu: apifilteridentifier {     case unknown(apifilteridentifier)     case = "everyone"     case team = "myteam" }  /* not compile */ enum enumtestdefaultassociatedvalues: apifilteridentifier {     case unknown(apifilteridentifier)     case everyone(apifilteridentifier = "everyone")     case team(apifilteridentifier = "myteam") }  /* compiles there better way? */ enum enumtestwithcustominit {      case unknown(apifilteridentifier)     case     case team      init(filteridentifier: apifilteridentifier) {         let everyone: apifilteridentifier = enumtestwithcustominit.everyonefilteridentifier         let team: apifilteridentifier = enumtestwithcustominit.teamfilteridentifier          switch filteridentifier {         case everyone:             self = .everyone         case team:             self = .team         default:             self = .unknown(filteridentifier)         }     }      func asidentifer() -> apifilteridentifier {         switch self {         case .everyone:             return enumtestwithcustominit.everyonefilteridentifier         case .team:             return enumtestwithcustominit.teamfilteridentifier         case .unknown(let filteridentifier):             return filteridentifier         }     }      private static var everyonefilteridentifier: apifilteridentifier {         return "everyone"     }      private static var teamfilteridentifier: apifilteridentifier {         return "myteam"     } }

i know bit old, work want?

typealias filteridentifier = string  enum defaultapifilters: filteridentifier {     case = "everyone"     case team = "team" }  enum apifilters {     case default(defaultapifilters)     case custom(filteridentifier) }  let everyonefilter = apifilters.default(.everyone) let teamfilter = apifilters.default(.team) let clownfilter = apifilters.custom("clowns_only")

Comments

Post a Comment

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall...
Read more

java - UML - How would you draw a try catch in a sequence diagram? -

-
Image
is there standard way of drawing try catch sequence diagrams? i've made attempt based on this feel end result doesn't feel right. code diagram based around: public static void save () { try { filehandle filehandle = gdx.files.external(file); filehandle.writestring(boolean.tostring(constantshandler.soundenabled)+"\n", false); (int = 0; < 5; i++) { filehandle.writestring(integer.tostring(constantshandler.highscores[i])+"\n", true); } } catch (throwable e) { } } my attempt note: know still need add loop. that's ok. fragments meant show conditional control flow in sequence diagram. superstructures puts limitations on use of fragments (see pp. 467 of ss2.1.1). should use critical region try part above. , option catch . however, keep telling can take quite freedom in using uml. it's language , such changes in life time. long reader ge...
Read more

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co...
Read more